I brought this up in What is a really old version of Perl?. As you have no doubt noticed by now, the majority of people posting in this thread have little to no understanding of how enterprise environments operate. There's a huge disconnect in the Perl community between developers and system administrators. Ironic, given Perl's roots. Sad too, of course. I doubt they even realize how hostile they come across or that the advice given may at times even be a career limiting move if followed. If there was a community wide effort to raise awareness, evangelize to vendors, etc. then maybe that would make a difference but I doubt the interest is there.
One thing you could try is putting your limitations in your signature (e.g. policy dictates that you have to use the Perl that ships with your distro and that it is against policy to download modules and manually install them (or just copy the .pm's in)m etc. and then reference that in your post. Then, you can at least berate someone for not reading the limitations in your environment.
-
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.
|
