A lot of times, Perl is used for stuff that doesn't have any official status or formal recognition, i.e., isn't on management's radar. The IT people have a problem of their own and solve it using Perl without going to management, or one of the programmers uses Perl to automate a task he used to spend time on, or cetera. Perl is really great for this sort of thing, partly because it's just generally flexible and capable but mostly because it tends to have a very low per-project overhead and make rapid development of such things practical. Projects that aren't on management's radar don't need a lot of non-programming overhead (i.e., nobody has to waste time doing flowcharts and UML diagrams and PowerPointless presentations and cost-benefit analysis on them), so the low programming overhead is more relevant and saves you a larger percentage of the overall project time.
"In adjectives, with the addition of inflectional endings, a changeable long vowel (Qamets or Tsere) in an open, propretonic syllable will reduce to Vocal Shewa. This type of change occurs when the open, pretonic syllable of the masculine singular adjective becomes propretonic with the addition of inflectional endings."
— Pratico & Van Pelt, BBHG, p68
-
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.
|
