develooper Front page | perl.perl5.porters | Postings from September 1999

Re: deprecating SIGDIE

Thread Previous | Thread Next
Raphael Manfredi
September 30, 1999 08:45
Re: deprecating SIGDIE
Message ID:
:IMO, eval should just do the local($SIG{__DIE__})

Tom's fix, as I understand it, provides the application with the ability to
fix one __DIE__ hook, and only one. That means no module should use it and
it must be reserved for the application. Else they must localize the change and
it is scoped at run-time, for the execution of a well-defined piece of code.

Just like signals. I'd hate to see a module change my signal handlers under
the hood, permanently. A localized change is OK (ala system()).

Upon pondering, I prefer Tom's approach.  __DIE__ is meant for exactly that.
A last chance to catch a die at the application level. Support for
post-processing to allow for rich exception handling/tracing needs to
be addressed though, so that people can convert all their existing code that
presently abuses the __DIE__ semantics.


Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About