Yes, but I guess what has me confused is why: perl -we '$x=1;$y=1;($x,$y)=("1",undef)' doesn't give any warning, while: perl -we '$x=1;($x,$ENV{y})=("1",undef)' does. Upon which I think I just found my solution... just use a temp variable for the two, and the warning goes away... although it seems strange that this warning is only for the list case, and that it only comes up when %ENV is being assigned to. If I use %E rather than %ENV, the error doesn't come up, either. Wierd.
Update: Duh, it's because I'm assigning undef to an environment variable Sigh. That warning was a bit too wierd for me to figure out. Chalk that one up to experience - I now have some more. Sorry for wasting your time - hopefully you can learn from this public "D'oh!" moment.
In reply to Re^2: Uninitialised value in list assignment
by Tanktalus
in thread Uninitialised value in list assignment
by Tanktalus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |