I've just gotten bit by this bug in AppConfig. The observant person will note that it is over 5 years old.
My question is this, do I work around it, possibly supplying a sub-class that applies the patch mentioned in the bug report, or just make a note of it in my own docs and go on? Beyond that, there are numerous bug reports for that module, seems a bit dis-concerting
for something that is included as part of CORE.
I decided to use AppConfig in the first place because it
was part of the CORE distro and had support for Getopt::Long as well as a config file. In fairness, the POD for AppConfig mentions that Getopt::Long support is "experimental".
Update: Double-checked and AppConfig is NOT part of CORE as pointed out below.
It helps to remember that the primary goal is to drain the swamp even when you are hip-deep in alligators.
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>
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
Want more info? How to link
or How to display code and escape characters
are good places to start.