Hi everyone,
Thanks very much for your replies, and sorry for my late reply, I've been very busy with other things.
I think what threw me off is how dire the warning I quoted sounds, but on re-reading the section of the documentation, it does sound more like the warning is referring to errors that happen during parsing (compilation). Unfortunately, I haven't yet found any background on the commit 19799a2 where the wording was introduced, the P5P archives seem to end a few months prior to the commit, and I haven't yet found anything in RT.
Anyway, taking all your replies together, it does seem like using $SIG{__DIE__} - at least as shown in the OP - is not such a bad thing, and since my handlers are generally installed during runtime and not compilation, and I'm not doing anything all too wild in the handlers, I think that for now I'll continue using code like what I showed. Thanks again!
Regards,
-- Hauke D
In reply to Re: How bad is $SIG{__DIE__} really?
by haukex
in thread How bad is $SIG{__DIE__} really?
by haukex
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |