This is a nice piece of obfuscation.

One way I would go about 'improving' it (err.. obfuscating it further) is remove the warnings (-w) option and 'strict' pragma. This will allow you to do a number of illegal moves and get away with it relatively clean. One thing I'll do is remove all occurances of the 'my ' declarations, they will no longer be needed. You could also look at replacing lengthy and rather descriptive variable names with something less readable.

Update: I'm not sure if this change would be most applicable if you were to write a japh, but you could also replace this:

$magritte = pack q\C4\, split /,/, qq;  80, 101, 114, 108; ;
[download]

with just:

$magritte = "\u$^X";
[download]

Initially, the former line looked to me quite obvious. However, as I look at it now.. the updated line doesn't seam as puzzling either. ;/ Oh, well, as I said, it might be good for a japh.

_____________________

# Under Construction
[download]

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.