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

> it doesn't work with more complex structures like hashes (or references to hashes)

To rephrase it, your problem are undefined elements of data structures like $h{x}.

I don't think there is any out of the box solution and you'd need to send a feature request.

As a side note: a hack could be to add a signal handler which parses the OP tree at the caller for all undefined entries .

But that's far from trivial.

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)

Je suis Charlie!}

Comment on Re^4: determine the variable causing the error: Use of uninitialized value

Replies are listed 'Best First'.
Re^5: determine the variable causing the error: Use of uninitialized value (hack) by LanX (Saint) on Apr 15, 2017 at 01:25 UTC
> As a side note: a hack could be to add a signal handler which parses the OP tree at the caller for all undefined entries . see RFC: Adding variable name to warning "Use of uninitialized value ??? in ..." Cheers Rolf _{(addicted to the Perl Programming Language and ☆☆☆☆ :) Je suis Charlie!}	[reply]
Re^5: determine the variable causing the error: Use of uninitialized value by ruqui (Acolyte) on Apr 16, 2017 at 02:37 UTC
Thank you for your suggestion Rolf, what should I do in order to send a feature request?	[reply]
Re^6: determine the variable causing the error: Use of uninitialized value by LanX (Saint) on Apr 16, 2017 at 11:38 UTC
I'm sorry but chances are too low, if you follow the discussion, especially the contributions by Dave_the_m you will see that is far too complicated too implement in core. update Anyway I've already shown code to help you in a pragmatic way Cheers Rolf _{(addicted to the Perl Programming Language and ☆☆☆☆ :) Je suis Charlie!}	[reply]