Re: Parsing command line options without knowing what they are

[GrandFather]

I don't know how your code is structured so may be the following doesn't apply, but if I were faced with the issue of code changes requiring their own sets of command line options I'd modularise the code and have each module register the options it uses at start up. That way the registration code can perform conflict checking and build the allowed list of commands for Getopt::Long at the same time.