Ronald J Kimball (lists.p5p): >Yes, Tom, we all understand that there are many cases where different Perl >syntax is compiled to identical opcodes, and that the interpreter warnings >reflect the compiled opcodes and not the original code. >But, neither the compiler nor the interpreter is going to fix the Perl code >that caused those warnings. That can only be done by the programmer, and >the warning messages should be optimized for the programmer, not for the >compiler or the interpreter. What are you going to do about this? othersideofthe:simon ~ % perl -we 'my $a; my $b="one"; print $a, $b' Use of uninitialized value in print at -e line 1. If you're optimising for the programmer, you tell him which variable it is. Patch welcome. -- You can't have everything. Where would you put it? -- Steven Wright