I don't believe this is a bug.
I think it is a bug because Deparse's output is not executable.
1;1 juerd@ouranos:~$ perl -e'sub foo () { 42 } print foo(), "-\n"'
42-
1;0 juerd@ouranos:~$ perl -MO=Deparse -e'sub foo () { 42 } print foo()
+, "-\n"'
print 42, "-\n";
-e syntax OK
1;0 juerd@ouranos:~$ perl -MO=Deparse -e'sub foo () { 42 } print foo()
+, "-\n"' | perl
-e syntax OK
42-
1;0 juerd@ouranos:~$ perl -e'sub foo () { 42 } print *foo{CODE}(), "-\
+n"'
42-
1;0 juerd@ouranos:~$ perl -MO=Deparse -e'sub foo () { 42 } print *foo{
+CODE}(), "-\n"'
print *foo{'CODE'}(), "-\n";
-e syntax OK
1;0 juerd@ouranos:~$ perl -MO=Deparse -e'sub foo () { 42 } print *foo{
+CODE}(), "-\n"' | perl
-e syntax OK
Undefined subroutine &main:: called at - line 1.
1;255 juerd@ouranos:~$
(In the last example, *foo{CODE} is undef, and undef->() gives an 'Undefined subroutine &main:: called' error.)
- Yes, I reinvent wheels.
- Spam: Visit eurotraQ.
