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

... which version of Perl are you using?

ruqui: This is an important question. The boon you seek was added with Perl version 5.10:

c:\@Work\Perl>perl -wMstrict -le
"print qq{perl version: $] \n};
 ;;
 my $x;
 print $x;
 printf '%s', $x;
"

perl version: 5.008009
Use of uninitialized value in print at -e line 1.
Use of uninitialized value in printf at -e line 1.

perl version: 5.010001
Use of uninitialized value $x in print at -e line 1.
Use of uninitialized value $x in printf at -e line 1.
[download]

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 ruqui (Acolyte) on Apr 13, 2017 at 19:23 UTC
AnomalousMonk it's correct what you say, but it only work with scalars, it doesn't work with more complex structures like hashes (or references to hashes): EXAMPLE: `perl -wMstrict -le 'print qq{perl version: $] \n};;; my $x; my %y= (" +h"=>1, "i"=>2); print $x, $y{x}; printf "%s", $x;'` [download] OUTPUT: `perl version: 5.018002 Use of uninitialized value $x in print at -e line 1. Use of uninitialized value in print at -e line 1. Use of uninitialized value $x in printf at -e line 1. </b>` [download]	[reply] [d/l] [select]
Re^4: determine the variable causing the error: Use of uninitialized value by LanX (Saint) on Apr 13, 2017 at 19:35 UTC
> 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!}	[reply]
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


Don't ask to ask, just ask
	PerlMonks