It's not like this is intended behavior :)

My other favorite is even sicker and more useful. Credit this time to audreyt++ who checked this into pugs with the commit message

do not mention $@% in the Makefile for portability

We had a one-liner that was breaking differently on different platforms. Insane desugaring to the rescue! 

-       \$(PERL) -MFile::Spec -e "my (undef, \$\$dir, \$\$file) = File
+::Spec->splitpath(shift); chdir(\$\$dir); system(q+$hsc2hs $hsc2hs_fl
+ags + . \$\$file);" \$<
+       \$(PERL) -MFile::Spec -e "sub p () { File::Spec->splitpath(ARG
+V->[0]) }; chdir((p)[1]); system(q($hsc2hs), qw($hsc2hs_flags), (p)[2
+]);" \$<

[download]
(The thing to note here is ARGV->[n].)

In reply to Re^3: Unobvious Pathological Code Snippets by gaal
in thread Unobvious Pathological Code Snippets by QM

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.