in reply to Mapster - co-operative maze mapping.

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.

Replies are listed 'Best First'.
I'm calling it Mapster!
by orkysoft (Friar) on Mar 18, 2001 at 02:49 UTC

    I'm calling the program "Mapster" :-)

    I'll consider the fatalsToBrowser, it'd give the users more of a clue about what is wrong when something goes wrong than just a white screen.

    However, when something goes wrong, it's usually because I'm fooling around with it, and I'll have it fixed in a matter of minutes, so it might not be that necessary.

    But thanks for your input. Also, I've fixed some more bugs. I'll update the code soon.

[reply]
[d/l]
Re: Re: Carp
by orkysoft (Friar) on May 05, 2001 at 09:07 UTC
    Well, I followed your instruction with the Mapster::TNG framework prototype, and boy, did it save me a lot of time! A shame I can only ++ a post once :-)
[reply]

In Section Cool Uses for Perl