I am not a web developer, so take these thoughts with some consideration.
Why not use a module like Carp to avoid use of die altogether? You'll generally get more helpful error messages this way, and then, for production you can easily switch Carp for a custom error handling package, without having to resort to handling the "real" error signals.
I would personally prefer to have errors with web pages redirected to a static or bullet-proof script by the server, rather than try to have the error-prone script handle them. You see this a lot with 404, but it may not be appropriate in situations with more subtle errors happening behind the scenes.
A good error message in your case will not tell the user anything other than, "You can't do that." If something the user has done is involved in the error, perhaps communicate this in terms that don't reveal your system's inner workings, but will allow them to understand what they need to do differently.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.