Re: Tiny Perl puzzle

in reply to Tiny Perl puzzle

<Reveal this spoiler or all spoilers in this node or all in this thread>

Can't test ATM :)

Cheers Rolf

(addicted to the Perl Programming Language)

update

tobyinc's analysis is correct! :)

one more reason to enforce use strict and 'warnings'...

Comment on Re: Tiny Perl puzzle Download Code

Replies are listed 'Best First'.
Re^2: Tiny Perl puzzle by Anonymous Monk on Jun 06, 2014 at 01:16 UTC
I wasn't even trying to guess what it would really parse as so I just Deparse and run it <Reveal this spoiler or all in this thread>	[reply] [d/l]
Re^3: Tiny Perl puzzle by davido (Cardinal) on Jun 06, 2014 at 18:43 UTC
I think B::Deparse gets it wrong -- as it sometimes does -- when you add `-p`: <Reveal this spoiler or all spoilers in this node or all in this thread> This is confirmed by the more low-level output of B::Concise: <Reveal this spoiler> Dave	[reply] [d/l] [select]
Re^4: Tiny Perl puzzle by Anonymous Monk on Jun 07, 2014 at 07:25 UTC
Look at the way Deparse uses whitespace, its subtle <Reveal this spoiler or all in this thread>	[reply] [d/l] [select]
Re^4: Tiny Perl puzzle by LanX (Saint) on Jun 07, 2014 at 15:38 UTC
I don't think so. did you recompile the output? I can't test ATM, but most likely it depends if a function is known at compile time. Contrary to AnoMonk I doubt space matters. Anyway IMHO the indirect object syntax should be deprecated.... Cheers Rolf (addicted to the Perl Programming Language)	[reply]
Re^5: Tiny Perl puzzle by Anonymous Monk on Jun 08, 2014 at 09:17 UTC
Re^6: Tiny Perl puzzle by LanX (Saint) on Jun 08, 2014 at 13:33 UTC

In Section Meditations