in reply to Re: Best practices for handling exceptions in die/eval style
in thread Best practices for handling exceptions in die/eval style

What eval doesn't hide is probably just a warning, not an error:
eval { warn "Boo" };

You can also hide them with

local $SIG{__WARN__} = sub {};

($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord }map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,

Replies are listed 'Best First'.
Re^3: Best practices for handling exceptions in die/eval style
by Anonymous Monk on Sep 06, 2018 at 01:39 UTC
    This doesn't work if something prints directly to STDERR, whether from perl or C or even a forked process, in which case the above mentioned redirection to devnull would be needed. However, that method is much more difficult to localize.