But let's not forget context -- useful error messages are all in the eye of the beholder.
For instance, if I'm batch processing files then I'd prefer to have the die() so that I can correct the error right away and get back on track. The more information, the better.
But if I'm a Web site visitor, I'd probably prefer to have the script die gracefully... in fact, I'd rather it gave me a simple message "Unable to complete request at this time, please click here to return to the page you were viewing. And then, of course, a detailed email message should be sent of to the site's programmers informing them of the problem and containing an much debugging information as possible.
It's all in the difference between programmers and end users, IMO.
In reply to Re: Re: Programming style question on where to use die
by jreades
in thread Programming style question on where to use die
by decnartne
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |