Actually, perl gets a lot of respect in my office. We're a pure unix shop, spun off from SGI and now 90% Linux. Every desk has a Windows box, but some of them are collecting dust in the corner.
The prevailing attitude is that perl has it's place, but if you need to write fast code (as opposed to writing code fast), you need C. Since we build video server platforms, I really can't argue. That said, perl has a place in the product and the company. Some of our database tools are perl, our test tools are mostly perl, and our product's internal diagnostic scripts are perl. Morover, every week or so I get a rush job to test something very specific or recreate a scenario that's surfaced in the field. Perl to the rescue.
-Logan
"What do I want? I'm an American. I want more."
-
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.
|
