From perlvar:
Remember: the value of $/ is a string, not a regex. awk has to be better for something. :-)
I suspect this not allowing a regex in Perl's record separtor $/ variable was the source of the famous
Larry Wall quote:
Hey, I had to let awk be better at *something*... :-)
Seriously, I've used both awk and Perl extensively over the years, and I'd say Perl wins easily for just about everything. Perhaps most tellingly, Perl scales better as programs tend to naturally grow larger over the years (as I similarly argued against Unix shell in Unix shell versus Perl). By all means compare Perl with Ruby and Python, but not awk: it's no contest.
-
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.
|
