in reply to Re^2: Using die() in methods
in thread Using die() in methods

You wrote:

"okay, let them to return the special sign to the caller and the caller will report to its' caller and so on - until the process pop up to the main module."

But perhaps you might have said instead: "let them to return the special sign to the caller and the caller will report to its' caller and so on - until it reaches a level I forgot to check for the special sign."

Exceptions are a special sign. But they are a special sign that you cannot forget to pass to your caller because Perl automatically passes it up and up and up until it finds a caller that is willing to do something useful with the special sign (i.e. catch the exception).

So throw exceptions! Don't return special signs!

If every level of caller needs knowledge about your "special signs", then your callers have too much knowledge about your class. Your callers have become tightly coupled to your class. This is bad.

"But I think the descision to die() can have only the main module."

I think you're confusing the decision to die() with the decision to exit(). I absolutely agree that the main script should be making the decision about when it exits. However, as you know, calling die() does not necessarily cause the script to exit; it can be caught by any level of caller and handled gracefully. It only causes the script to exit if an error occurs that nothing is able to handle.