•Re: Use B::Deparse to see why

probably lies in the fact that @-interpolation is a quite new invention (5.6 AFAICR).

Oh, you young'uns. {grin}

@-interpolation in a string dates back to Perl version 5.000. It's the reason that you get the fatal error when you have something like "merlyn@stonehenge.com".

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

Comment on •Re: Use B::Deparse to see why

Replies are listed 'Best First'.
Re^2: Use B::Deparse to see why (age) by tye (Sage) on Sep 23, 2004 at 16:21 UTC
@-interpolation in a string dates back to Perl version 5.000. Oh, you young'uns. (: It dates back way before that. I've personally used @-interpolation in strings in Perl v3. `> perl4 -e "print qq<(tye@ARGV)\n>" this that (tyethis that) > perl4 -e "print qq<(tye@foo)\n>" this that (tye@foo)` [download] What changed with Perl5 was that the DWIM of optional interpolation was removed. The only reason the second example needs to be fatal in Perl5 is so that the change in behavior was not a "silent change". I suspect you know all of this, but your node was at least misleading so I felt clarification was in order. - tye	[reply] [d/l]
•Re^3: Use B::Deparse to see why (age) by merlyn (Sage) on Sep 23, 2004 at 16:23 UTC
Oddly enough, that's what I was trying to think, but it was too early in the morning for me to remember that. I kept thinking "wasn't @foo interpolated as far back as perl 2?" But then I couldn't remember why the error was added in perl5. Thanks for the clarification. I'm getting too old for this. {grin} -- Randal L. Schwartz, Perl hacker Be sure to read my standard disclaimer if this is a reply.	[reply]


laziness, impatience, and hubris
	PerlMonks