Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Mastering Regular Expressions, by Jeffrey Friedl is so good, I just don't see how anyone can do without it if they're using regular expressions at all.

If you've ever been tricked by greedy quantifiers, lazy regexp engines, confusing lookaheads, backreferences, POSIX character classes, inline eval, recompilation, sluggish alternation, and so on, you need this book. If you don't recognize some of those terms, you really need the book. I know that the Perldocs are touted as being the definitive source on Perl, but in the case of Regular Expressions, the Owls book has got to be the standard work.

Every time I see regular expression related questions posted to Perlmonks, Usenet, or anywhere else, I think, "Why didn't this person just read Mastering Regular Expressions?" It's the book that turns run of the mill Regular Expression authors into Masters of the Craft.

When you read it, be prepared to start seeing everything in life in terms of regular expressions (except for irregular things, of course). And be prepared to start counting to ten a lot before posting replies when you see questions on by those who obviously haven't been to the fountain yet. You can spot them immediately. It's ok, your work is easier than theirs because you took a few days and read this book. Go easy on them.

If there ever were a mountain with a guru sitting atop in a secluded hut, Friedl would be that guru, and the otherwise arduous journey to the mountain top would be facilitated by the Owls book like an air-conditioned tram car. The journey back down, of course, would be in the slipery slide of an efficient regular expression.


"If I had my life to do over again, I'd be a plumber." -- Albert Einstein

In reply to Re: Mastering Regular Expressions by davido
in thread Mastering Regular Expressions by splinky

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others scrutinizing the Monastery: (4)
    As of 2018-06-19 03:32 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (111 votes). Check out past polls.