I encountered something similar with destructors a while back. My case was that the eval{} block in my destructor was actually writing over the previous error status, and therefore making it looks as though there *was* no error.
DESTROY and eval definitely don't play nice in some edge cases. Module authors ought to be careful not to introduce code like this (reminder to self)
In reply to Re: An uncatchable die
by lestrrat
in thread An uncatchable die
by dws
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |