Look at the way Deparse uses whitespace, its subtle

did you recompile the output?

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

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

it depends! ;-)

> > most likely it depends if a function is known at compile time

> perl
open ONE, ">", "/tmp/tst";

sub ONE { "@_ \n Space doesn't matter! \n" }

print ONE ( TWO );          # sub-call

__END__
TWO 
 Space doesn't matter!
[download]

update

ALSO:

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

BUT:

> perl
open ONE, ">", "/tmp/tst";

print ONE(TWO);             # sub-call

__END__
Undefined subroutine &main::ONE called at - line 3.
[download]

Cheers Rolf

(addicted to the Perl Programming Language)