Those have to be very good reasons, but they exist.
Seen twice this year: a process chain built on sh, java, perl, python, and two other "languages". There were several people that knew what the complete process was supposed to do, but none that knew all steps. The programmers that created the java and the python "chain-link" had left the company and none of the other developers knew how to change that code if it were broken. We decided to replace the functionality of the weak chain pieces with one of the languages that the remaining programmers were comfortable with. It was my luck they picked perl. Process chain back in working - and maintainable - order. I completely realize that if their knowledge of perl was close to zero and they picked python, that would have been as good a choice at this point in time.
Enjoy, Have FUN! H.Merijn
-
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.
|
