in reply to Re^5: why did i die?
in thread why did i die?

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.

Replies are listed 'Best First'.
Re^7: why did i die?
by BrowserUk (Patriarch) on Apr 02, 2014 at 11:34 UTC
    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.

    I don't disagree with that, but the categorisation should be done but the author of the code that can generate the exceptions; not after-the-fact by a third party logging package that has no knowledge of the code.

    That's like giving the telephonist responsibility for deciding who gets an emergency response, based upon the their interpretation of the description provided by a 5 y/o child. "Mommy's asleep and won't wake up!"

    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

      Totally true. However... it is not in the design of our beautiful language. There is even no guideline about what is preferred. So, the only way left is to do the best you can... and I can do a little better I hope. At least, I hope to be able to separate the three causes for filling $@.

      It's not that I am not aware how bad the situation is, just that I try to make the best of it. And yes, the telephonist will decide urgency based on the 5yr old's description.

[reply]

In Section Seekers of Perl Wisdom