I agree with your statements about the importance of regular expressions for a Perlist, but I have also learned a metric crapton about regular expressions in general (and Perl regexen in particular) without ever having read Mastering Regular Expressions.
Would I learn more if I read that book? Oh, certainly -- and I may well read it some day. Is it one of the core three books of a central trilogy of books that anyone getting into Perl should probably read first, specifically for purposes of learning Perl? I don't really think so. I'm of the opinion that learning enough about regexen to get by, and spending some time learning some other concepts that are also important, is more important for such a student of Perl. A deeper understanding of regexen than can be had by getting familiar with Perl in general and learning to navigate perldoc is a matter of specialization rather than of general Perl competence, I think.
I suppose your mileage may vary -- but that's kinda my point.
| print substr("Just another Perl hacker", 0, -2); |
|
- apotheon
CopyWrite Chad Perrin |
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
