If the eval'd code already catches these errors, then it is not the responsibility on "my level eval" anymore that it is treated correctly. I only want to be able to handle accidents which happen unhandled.
There are many frameworks which offer many levels of messages, like syslog. When you maintain larger applications, you often route messages based on the seriousness (level) of the message. For instance, you make panics and alerts very visible, and ignore warnings. So: many people agree that Perl's one-level-fits-all concept is too limited.
You: really don't think there is any sensible way for a generic logging module to categorise the seriousness of exceptions thrown by unknown code.
That's not what I am looking for: I only want to be able to separate Perl's internal die's from user-program die's. Other problems are solved (or unsolved) in other ways.
In reply to Re^6: why did i die?
by markov
in thread why did i die?
by markov
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |