in reply to RE: Obfuscated? no.... ;-)
in thread Obfuscated? no.... ;-)

Of course that is obfuscation... and it's neat and clean...

I thought it funny that a ( suposed :-) comment is used in the code...

I could have said this though... if you like... is it good enough for you?

%_=(Just=>q=%20==>another=>q=%20==>Perl=>q=%20==>Hacker=>q=%0A==>)=>
print map{$_->[2]=~s=[^->]?(.[^->])=chr(hex($1))=e;$_->[0]=>$_->[2]} 
sort{$b->[1]cmp$a->[1]}map{[$_=>m=[^->]+([aeiou])==>$_{$_}]}keys %_;
Did I mention that I always do my 'one liners' under strict and -w

I belive that good practices should go through every code you write... but that's another thread.

--
Casey

Replies are listed 'Best First'.
RE: RE: RE: Obfuscated? no.... ;-)
by mcwee (Pilgrim) on Jun 02, 2000 at 22:35 UTC
    Hell, the original JAPH was good enough for me-- I'm sorta charmed by its duality. Hidden-in-plain-view, after a fashion.

    The Autonomic Pilot

RE: RE: RE: Obfuscated? no.... ;-)
by mcwee (Pilgrim) on Jun 02, 2000 at 22:36 UTC
    Hell, the original JAPH was good enough for me-- I'm sorta charmed by its duality. Hidden-in-plain-view, after a fashion.

    The Autonomic Pilot

RE: RE: RE: Obfuscated? no.... ;-)
by KM (Priest) on Jun 02, 2000 at 22:45 UTC
    Actually, I don't find either too obfuscated. You can tell exactly what each is doing just by looking at it, and after reading the code over once or twice you can see how it is doing it. Maybe I would say they are 'neato', but not very obfuscated.

    Cheers,
    KM