- Because perl is interpreted, as opposed to compiled, the development time is cut down as the compliation step is non-existent. (Do note, of course, that perl can be compiled to native executables to speed things up once scripts are debugged completely).
- The perl code will remain portable across platforms if that so happens to the case. You'd have to recompile C scripts and account for any vendor differences with C.
- Perl's much less prone to 'buffer overflow errors' compared to C, given that you don't have direct access to memory. You still need to run with strict, -w, and -T, but a lot of security headaches can be removed in this aspect.
Update: as pointed out to me, perlcc'ing a perl script does not gain any benefits during runtime compared to intepreting that script, so the second comment on the first point is null & void. However, the fact that avoiding the compilation step to just test and debug code is a definite benefit.
Dr. Michael K. Neylon - mneylon-pm@masemware.com
||
"You've left the lens cap of your mind on again, Pinky" - The Brain
-
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.
|