While I can see how Stephen is looking at this as an obfuscation-in-progress, and others are looking at it as just plain obfuscated, this type of thing is a great example of why I love playing around with Perl. Don't get me wrong, I certainly thought merlyn had left out a few lines when I first looked at it, but after a couple of minutes it really started to look beautiful (I'm sick, I know...). In this fine example, merlyn:
- didn't redefine any defaults
- didn't use any obscure, poorly documented features
- didn't even use single-letter variable names
- heck, it's even full of wasted spaces

He simply made excellent use of the well-documented default behaviours which even I use every day. It still amazes me that St.Larry (and some Perl elves) thought up all these behaviours which often look odd to me at first, but eventually dovetail together so well it's hard to imagine all of these uses weren't considered. Maybe after I've been here long enough I'll be able to come up with better ways to fit the parts together too.

--
I'd like to be able to assign to an luser

In reply to Re: (thoughts on) Detect common lines between two files, one liner from shell by Albannach
in thread Detect common lines between two files, one liner from shell by merlyn

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.