Japhaholic

[dsb]

Okay. I'm going a little JAPH happy. I like 'em though because they are helping me learn about new(to me) functions in Perl. Anyway, here's another, making use of the 'map' function which I keep seeing.

#/4a/75/73/74/20/41/6e/6f/74/68/65/72
open(FH,$0)||die;while(<FH>){chomp;if
(m/^#(.*?)$/){$_=$1;@_=map {split'/'}
$_;foreach(@_){print pack "H*", $_;}}
}print "\n";########## kel ##########
#/20/50/65/72/6c/20/48/61/63/6b/65/72

- kel -

[BooK]

You call this obfuscation?

You make not use of context, you explicitely use $_, @_, you never even try to hide something... It's so clear, you just read it and understand the whole thing!

I showed it to a non-Perl programmer, explaining what split, etc did... I mean, we didn't even need to run the stuff to know what it did and how!

Having all lines of the same length is not enough to qualify, in my view... Except if you lines are 4 characters long.

Update: So that people stop downvoting me, here my shorter (but not more obfuscated) version:

print+map{pack'H*'
,$_}('4a7573742041
6e6f74686572205065
726c204861636b6572
0a0d'=~m/(..)/g)

It doesn't read its own source code, makes use of the fact that . doesn't match newlines, chains everything in one statement, etc...

[dsb]

Tell me how you really feel why don't you. :) - kel -

[MrNobo1024]

Here are a couple of tricks which might help you with your next JAPH:

if you want to open your program's own source, instead of "open(FH,$0)" you can just use "open+0", and then you can use <0> to read lines.

Instead of using \n for newlines use the variable $/ which is automatically set to a newline when your program starts

[Elgon]

I write JAPHs for this reason also, however reading them is seriously good for your Perl knowlege - although I've never been tempted to use some of the more twisted mechanisms myself ;-)

Elgon