in reply to Re: Tiny Perl puzzle
in thread Tiny Perl puzzle

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>

Replies are listed 'Best First'.
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:

    My theory: When Deparse tries to add parens wherever it can, it treats the first two as a function call (which was my first guess too). But as tobyink correctly surmised, that first two is treated by print as a filehandle.

    This is confirmed by the more low-level output of B::Concise:

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

    Dave

[reply]
[d/l]
[select]
[reply]
[d/l]
[select]
[reply]

        I can't test ATM

        You gotta stop saying that :)

        Contrary to AnoMonk I doubt space matters.

        Sure it does, it matters how Deparse places the space, because it matters to perl 

        $ perl -w
print(two (('two' == 'five') ? 'true' : 'false'));
Unquoted string "two" may clash with future reserved word at - line 1.
^Z
Name "main::two" used only once: possible typo at - line 1.
Argument "five" isn't numeric in numeric eq (==) at - line 1.
Argument "two" isn't numeric in numeric eq (==) at - line 1.
print() on unopened filehandle two at - line 1.

        [download]
        That is exactly as deparsed with -p, behaves exactly like the original
[reply]
[d/l]

In Section Meditations