Re^2: Use Getopt::Long even if you don't think you need to

It's always easy to criticise (at least I sense some criticism in your post :) ... but I'm wondering what alternative user interface you would suggest if you want that functionality? Some config file, or even a GUI (*shudder*), or what else? Not wanting to start a flame war, but I think command line options aren't that bad after all, provided they come with reasonably accessible documentation and have sensible defaults, so you'd only need a few of them anyway in most cases.

Comment on Re^2: Use Getopt::Long even if you don't think you need to

Replies are listed 'Best First'.
Re^3: Use Getopt::Long even if you don't think you need to by Argel (Prior) on May 19, 2008 at 18:58 UTC
When things get complex like that I think a config file should be an option and a GUI to help manage it might also be nice. But keep in mind you can always put everything into a shell script with each option on its own line (just use a backslash to continue the command on the next line). In effect the shell script then becomes a config file (albeit a weak one).	[reply]