Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Are You Sure You Want To Do That Which You Don't Understand? 1 Comment More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • One of the problems with development of large programs/systems is that errors/conditions seem to get summarized, more and more, the closer they get to the user. This tends to remove most of the useful information for the knowledgable end-user. Even if the errors are annotated as they move up the call tree, there is a tendancy to only display one unified message to the user -- I'm assuming to avoid confusing them.

    Just yesterday on my Mac, Norton AntiVirus said something meaningfull like "Virus updated failed". Great. If there was a "More Details" button I could at least have a chance of determining if there was a network problem, the server was down, a local disk problem, whatever. As it was I felt like a dumb user, which in this case I was, and was forced to try the usual braindead things like: quit/relaunch, try again, reboot.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.