You're misinterpreting my comment. Most sysadmins that I've worked with know a little perl and tend to write quick scripts to get things done, e.g. find all files like this and change this word in them. These are one-offs, and it's no crime that they aren't that pretty. The trouble is, sometimes these get handed to someone for revisions and maintenance, and the person they get handed to doesn't know much about perl and doesn't realize that perl can be beautiful when necessary. This can lead to misconceptions.
So, I mention sysadmins because the nature of the job as I've seen it (overworked, trying to fix an emergency, not usually a full-time coder) tends to breed some ugly perl. It wasn't meant to be a slur, and I'm sorry if it sounded like one. I could say the same thing about people learning perl by looking at Matt's Script Archive or some other bad CGI stuff, except that Matt really has no excuse for his code.
-
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.
|
