JAPHs are often obfuscation, and obfuscation is a way to "strut your stuff", much in the same way modules and articles and "op" status on a Perl channel on IRC somewhere is.

They're by no means a "rite of passage" into a secret "Perl Cabal*". They're just fun ways to exploit Perl (either its loose syntax, or its bugs). That being said... 
# my message should've started with this:

{ 
  $_ = q"I'm";
  * == \q;
  s/$/ Just Another Perl Hacker/;
}

s+(.).+$1+;
$_.=$= if $= !=~ s.\.\..\U$&.;
$= ==~ s=.+(o)+.=\U$1= or tr!Perilous / Treacherous Tracks\n!!d;
$= !=~ s/..$/q ... reverse $&/e and print;

[download]
The secret password is 'GRT'. You know the meeting place.

japhy -- Perl and Regex Hacker

In reply to Re: JAPH and Perl Monks by japhy
in thread JAPH and Perl Monks by thaigrrl

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.