One of the scripts in question is being run on offsite systems, which have a default perl config (in house Solaris packaged perl build) that has a very limited number of additional modules. The last time we got the package rebuilt with an additional module, it took 6 months from request to distribution - and that was a critical requirement. Anything not considered critical would be more trouble than it's worth from my POV.
I suspect that's one of the few reasons for reinventing the wheel :)
One of the other scripts I'm considering for this may be better to use a different method, since I'm considering contributing it to the SpamAssassin project - meaning it would probably be best to use Config::Inifiles or YAML (XML would be a real learning curve at this point, but not something I'm opposed to).
-
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.
|