http://www.perlmonks.org?node_id=619320


in reply to Offuscamento Divino

I think it's beautiful, though I don't understand why it doesn't work. If I decompose it, it still doesn't work, but when I perltidy the soutce, it works. Weird

e.g. thist does not work:

   # perl xx.pl

whereas this does work:

   # perl -0 -MPerl::Tidy=perltidy -ne's/;eval//;eval;perltidy source=>\$_,destination=>\$y;eval$y' xx.pl

update: this also works:

   # perl -0 -ne's/;eval//;eval;eval' xx.pl

Enjoy, Have FUN! H.Merijn

Replies are listed 'Best First'.
Re^2: Offuscamento Divino
by Tux (Canon) on Jun 06, 2007 at 17:27 UTC

    liverpole wanted to know the systems where I tried. So far all behave the same. All systems have perl-5.8.5, 5.8.7, or 5.8.8 all with defined-or. All are non-threaded. There is no diff between 64bitint or 64bitall.

    HP-UX 11iv2 example (64bitall)

    102 > perl xx.pl
103 > perl -0 -ne's/;eval//;eval;eval' xx.pl
Unquoted string "white" may clash with future reserved word at (eval 3
+) line 1 (#1)
    (W reserved) You used a bareword that might someday be claimed as 
+a
    reserved word.  It's best to put such a word in quotes, or capital
+ize it
    somehow, or insert an underbar into it.  You might also declare it
+ as a
    subroutine.

104 > perl -MV=Tk
Tk
        /pro/lib/perl5/site_perl/5.8.7/IA64.ARCHREV_0-LP64/Tk.pm: 804.
+027
105 >

    [download]

    Enjoy, Have FUN! H.Merijn
[reply]
[d/l]

In Section Obfuscated Code