Yes there are awk guys out there. I get awk code and have to deal with it from 2 people who will remain anonymous. Their awk code is good awk code. I write Perl stuff that "stitches their awk together" and we get a good result (meaning application that works).
As far as "Perl experts" go, some folks are considerably better at Perl than others. I remain skeptical that a well coded Perl app would be of lower performance than an awk app. I will add that fewer lines of Perl doesn't necessarily mean higher performance. I will also add that the three of us have an app and process that works and we don't see any need to optimize the performance. I would argue before taking on an "optimizing" mission, a relevant questions is: does anybody care and does it matter? The main thing is: does it work?
-
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.
|
