On 8/17/07, Chas Owens <[EMAIL PROTECTED]> wrote: snip > which still works in Perl 5.8.8, but probably shouldn't. I thought > they were going to fix this after Perl 5.6.1, but apparently it is > still around (or has reemerged). Maybe Perl 6 will finally kill it (I > have to test it in Pugs now). snip
Yes, I am pedantic, it is a disease, pity me. Apparently I got the time frame right, but the outcome wrong: there was talk of adding a warning, but obviously nothing came of it. from http://www.perl.com/pub/a/2000/05/p5pdigest/THISWEEK-20000521.html#my_x_if_0;_Trick Some people suggested documenting this 'feature'. Tom said that Larry had told him not to do that because he didn't want to reply on supporting it. Larry affirmed this: Jan Dubois: I think this behavior is a side effect of the implementation and shouldn't be documented as a feature. It should at best be "undefined" behavior that may change in the future (IMHO). Larry: In Ada parlance, use of this feature would be considered erroneous. Simon Cozens said to me later that if p5p can't understand the 'feature', it should not be documented as a feature. I think there's some truth in that. Barrie Slaymaker suggested that Perl issue a warning in this case. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/
