But it should be feasible to write a an op-code walker catching them at compile time in the UNITCHECK phase.
D:\>perl -MO=Terse -E "use strict; say @@" LISTOP (0x2820630) leave [1] OP (0x2820600) enter COP (0x2820670) nextstate LISTOP (0x2820700) say OP (0x28206d0) pushmark UNOP (0x2820740) rv2av [2] <-- array PADOP (0x2820778) gv GV (0x1dede0) *@ <-- of glob *@ -e syntax OK D:\>perl -MO=Concise -E "use strict; say @@" 7 <@> leave[1 ref] vKP/REFC ->(end) 1 <0> enter ->2 2 <;> nextstate(main 48 -e:1) v:%,*,&,{,x*,x&,x$,$,469764096 ->3 6 <@> say vK ->7 3 <0> pushmark s ->4 5 <1> rv2av[t2] lK/3 ->6 <-- array 4 <#> gv[*@] s ->5 <-- of glob *@ -e syntax OK
Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery
FootballPerl is like chess, only without the dice
In reply to Re^4: Code Loop?
by LanX
in thread Code Loop?
by bitman
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |