An intesting collaborive application.

Your development efforts, and the lives of those who try to run your scripts elsewhere, might be eased somewhat if you were to add use CGI::Carp qw(fatalsToBrowser); to the tops of your scripts. Then you could safely add error checking to all of your open calls.

Before you spring this on the general populus, cleaning up your die messages might be in order. Reporting "404" for open failures is at best cute, and at worst misleading. If someone emails you to report "I tried your stuff and got a 404", you're not going to know whether it was an HTTP 404 or a 404 from one of your error messages, and you'll have to go an extra round of email before you can sort out the problem.

In reply to Re: Co-operative maze mapping by dws
in thread Mapster - co-operative maze mapping. by orkysoft

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.