Don't get me wrong, regexes have their place in perl. It's part of what makes perl perl. However, I think that people have the tendency to look at every problem as a regex problem (or more generically as <insert your favorite paradigm here> problem). And, when that happens, you have people writing unnecessarily complex regexen to make the square peg fit in to the round hole. In this case, the OP had a problem where s/he had a delimited record format. If that doesn't scream split, I'll eat my hat. But, the OP had a predisposition towards using regexen at the detriment of not only readability but simplicity.
Also, I take issue (though not on a personal level) with saying that something has to be done in a certain way. Not only are you working to the exclusion of other, possibly better tools, but in some cases, your chosen tool doesn't even make sense.
thor
-
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.
|
