Re^2: determine the variable causing the error: Use of uninitialized value

... uninitialized value ... is a warning, not an error (unless it's escalated to FATAL-ity); no exception is thrown.

Give a man a fish: <%-{-{-{-<

Comment on Re^2: determine the variable causing the error: Use of uninitialized value Select or Download Code

Replies are listed 'Best First'.
Re^3: determine the variable causing the error: Use of uninitialized value by marinersk (Priest) on Apr 14, 2017 at 04:42 UTC
Thank you -- That was the closest thing I could come up with, so I should trust my instincts more. So -- Since you didn't mention one, I presume there isn't an `eval`equivalent which does catch warnings?	[reply] [d/l]
Re^4: determine the variable causing the error: Use of uninitialized value by kcott (Archbishop) on Apr 14, 2017 at 05:22 UTC
You could use `{ local $SIG{__WARN__} = sub { ... }; eval { ... }; }` [download] to trap the warning and do something special with it. However, I can't see that helping with identifying uninitialised values. There's example code in perlvar: %SIG. — Ken	[reply] [d/l]
Re^4: determine the variable causing the error: Use of uninitialized value by karlgoethebier (Abbot) on Apr 14, 2017 at 13:02 UTC
"...catch warnings?" With `use warnings FATAL => qw(uninitialized);` it works with `eval` as well as with Try::Tiny. As AnomalousMonk suggested. ŤThe Crux of the Biscuit is the Apostropheť Furthermore I consider that Donald Trump must be impeached as soon as possible	[reply] [d/l] [select]