![]() |
|
good chemistry is complicated, and a little bit messy -LW |
|
PerlMonks |
Re: die/warn signal handler best practice questionsby TOD (Friar) |
on Oct 08, 2007 at 03:50 UTC ( #643376=note: print w/replies, xml ) | Need Help?? |
in general: don't trust people telling you to never do this or that. ;) second, i think you overestimate the complexity of that handler problem. as you can see from e.g. perldoc -f local, it's very easy to let every process take control over its own reactions on __DIE__ and __WARN__ signals. and if you strictly distiguish between the process and the modules it loads it becomes fairly clear (to me), that a module should simply die, whilst the process redirects that signal to maybe a logging thread or any other appropriate stuff.
-------------------------------- masses are the opiate for religion.
In Section
Seekers of Perl Wisdom
|
|