These two pieces of code do the same thing. Can you see what they do before reading the rest of this? 
% perl -E'say for&{sub{"\U\x{fb01}\x{fb03}"=~/.{0,2}.{0,3}.{0,3}.{0,4}
++(?{$_[++$#_]=rand})(*FAIL)/||pop;@_}}'

% perl -E'say for(*100=sub{$_[0]?(rand,(*{$_[0]-1}=*{$_[0]})->($_[0]-1
+)):()})->(100)'

[download]
If you want, run them so you can see what they do. Don’t worry: they’re perfectly harmless. Try perltidy on them: go ahead, I dare ya. :) And for the first, I would also suggest adding -Mre=debug. That should make it more obvious. Heck, might as well run them under the debugger, just in case.

Good luck!

<Reveal this spoiler or all in this thread>

Summary

Which one do you like better, and why?

In reply to Unearthed Arcana by tchrist

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.