Sigh...

I think this proves I have no talent for obfuscation. Ah well, a few downvotes might lower my embarrassingly high XP to nodes ratio.

But anyway.

print "Not an Obfuscation\n\n"; # BooK food ;) @_=#Happy Birthday ailie map{chr}112,114,105,110, 116,32,109,97,112,123,99 ,104,114,125,54,54,44,49 ,49,52,44,49,48,53,44,49 ,48,51,44,49,48,52,44,49 ,49,54,44,51,50,44,57,56 ,44,57,55,44,49,48,56,44 ,49,48,56,44,49,49,49,44 ,49,49,49,44,49,49,48,44 ,49,49,53,44,52,52,44,51 ,50,44,56,48,44,49,48,49 ,44,49,49,52,44,49,48,56 ,44,51,50,44,55,55,44,49 ,49,49,44,49,49,48,44,49 ,48,55,44,49,49,53,44,49 ,48,44,57,57,44,49,48,49 ,44,49,48,56,44,49,48,49 ,44,57,56,44,49,49,52,44 ,57,55,44,49,49,54,44,49 ,48,53,44,49,49,48,44,49 ,48,51,44,52,52,44,51,50 ,44,57,55,44,49,48,53,44 ,49,48,56,44,49,48,53,44 ,49,48,49,44,51,50,44,49 ,49,53,44,49,48,57,44,49 ,48,53,44,49,48,56,44,49 ,48,49,44,49,49,53,44,53 ,57,44,49,48,44,55,50,44 ,57,55,44,49,49,50,44,49 ,49,50,44,49,50,49,44,51 ,50,44,54,54,44,49,48,53 ,44,49,49,52,44,49,49,54 ,44,49,48,52,44,49,48,48 ,44,57,55,44,49,50,49,44 ,52,52,44,51,50,44,49,49 ,53,44,57,57,44,49,49,52 ,44,49,48,53,44,57,56,44 ,49,48,49,44,49,48;for$x (@_){$_.=$x};eval

-- 
Tom Waddington

Replies are listed 'Best First'.
Re: It's the thought that counts
by BooK (Curate) on Feb 14, 2001 at 17:21 UTC

    Well, then at least I don't have to vote on it... ;-)

    Strange, you actually made your program several times longer than the original (the part that's eval'ed). Not that size does really matter, but I was kinda puzzled by all those 44...

      You were puzzled? Maybe it's not as bad as I thought. :)

      To be honest I had much grander plans for this one but, depending on how you look at it, I ran out of either talent or time. Maybe I should have postponed it until next year.

      -- 
      Tom Waddington

        Well, even though I don't like "obfuscation" schemes that include calls to crypt, unpack or chr, I have to admit I don't know the ASCII table by heart. :-)

        So, I noticed all those 44s, decided I could at least change the eval for a print, and see what it actually did (mind you, I didn't guess... but the way to do it is still, er, poor).

        If the main point in an obfuscation is based on s///, crypt, or chr to make it hard to understand, you can be sure I won't like it. Try to do the same thing in a completely unnatural and complicated way, and there you will have me try to understand what it does, parsing it by hand, and so on...