Investigate using gengetopt for command line options

[dharple]

gengetopt allows for abstraction of the command line options. Review whether it's a good fit.

[dharple]

It's interesting. Here's how it would work:

We would create two .ggo files, one for inline detox and one for detox:

package "detox"
version "1.3.0"

option "config"          f  "choose which config file to use" string typestr="filename"
option "dry-run"         n  "do a dry run (don't actually do anything)"
option "inline"          -  "run inline mode"
option "list"            L  "list available sequences and exit\nwith -v ... dump sequence contents"
option "recursive"       r  "be recursive (descend into subdirectories)"
option "remove-trailing" -  "remove trailing _ and - before or after a period"
option "sequence"        s  "choose which sequence to detox with"

Then, to build them, the line would look something like this:

gengetopt < parse_options_detox.ggo --file=parse_options_detox --func-name=parse_options_detox --arg-struct-name=detox_options --unamed-opts

Unfortunately, because ggo generates its own structure (per include file), we can't use the same structure prefix. Also, because you can't fully rename the functions inside of the generated .c file, we might also need to create two similar parse_options.c files, to dump the output from this in to the existing (neutral) structure.

I'm not sure all of that is worth the effort.