While policy does not explicitly forbid CPAN modules, they are completely unsupported inhouse. Without inhouse support there's too many hurdles to overcome to use CPAN modules effectively. It's more like enforcing a ban by attrition than an outright ban.
I'm working on 'em though projects like the one I'm working on currently will go a long way to insinuate Perl a little deeper into the corporate culture/infra-structure
For now that has to be the best next step. Once they are
comfortable with that then progress on CPAN can be made. I know that might sound a bit backword to outsiders but I've been advocating actively for a few years here. Patience and solid code in the clutch is the best course for now :)
coreolyn
-
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.
|