in reply to A strange old perl bug: "Can't use an undefined value as an ARRAY reference" error given for a misleading/wrong line number

I think most would agree that it is easily identifyable as an issue in perl v5.8.8.

This was a known limitation of older Perl's (pre-5.10 from memory).

Basically, any warning or error resulting from an if or elsif condition within an if/elsif/else cascade was reported with the line number of the opening if.

There are at least a couple of threads around here -- including one of my own -- that talk of this. If I succeed in digging one or more of them up, I'll update.


With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.


Comment on Re: A strange old perl bug: "Can't use an undefined value as an ARRAY reference" error given for a misleading/wrong line number
Re^2: A strange old perl bug: "Can't use an undefined value as an ARRAY reference" error given for a misleading/wrong line number
by Athanasius (Monsignor) on Feb 13, 2013 at 03:44 UTC