in reply to The Latest Craze

This is a really really good obfuscation. Not that difficult to work out, but very creative. Bravo.

On a side note, it worked well with my perl 5.005_3, but not with 5.6 (prints a blank line). The following adaptation does work with 5.6, but not with 5.005_03 (Global symbol "$uo" requires explicit package name at (eval 1) line 2.). Go figure.

eval'use strict;$uo';@_{split//,eCVJABDdEeSFeNeeGaeIHQecePMLR.
TeeUeeeZYeKeeOXebWeeee}=split//,uc$@;print@_{sort+keys%_},"\n"

[download]

Replies are listed 'Best First'.
Re: Re: The Latest Craze
by japhy (Canon) on Feb 23, 2001 at 03:14 UTC
    Yeah, well it took me forever to figure out how to capture Perl's builtin warnings. It is quite difficult. I had to resort to capturing a fatal error message (I was using a different method, but it didn't work -- trying to get the "Useless use of variable in void context" message, but couldn't figure out HOW).

    Then it occurred to me -- how about I see if there's an error message that contains all the letters I need, and indeed there are several. (This is a sign that Larry played Zero-Wing.)

    And it irks me that Perl has changed the error handling/catching method in 5.6.0. Oh well.

    japhy -- Perl and Regex Hacker

[reply]

In Section Obfuscated Code