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.