The way that I tend to think of “very-high level languages” like Perl is that they represent a large wad of very cleverly-written "C" and assembler code that I didn't have to write or debug. The moment my program starts, it's running within the envelope of what is actually a very complicated runtime environment... no thought required. Tools like Perl allow us to focus on what matters to a particular application, and to ignore (or simply take for granted) all the rest. For all its warts, Perl definitely moves the freight.
I'm very reluctant to blame any project failure at all upon the language(s) or tools that were used to build it. The true cause of the failure usually has two ears, and a vacuum in-between. :-D
-
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.
|
