Hi nice to hear about the new gengetopt version. I kindly ask what's about this groupoption refactoring?
-- Papp, Gyozo Virusbuster Kft _____ From: Papp Gyozo (VBuster) [mailto:[EMAIL PROTECTED] To: Users list for gengetopt [mailto:[EMAIL PROTECTED] Sent: Fri, 15 Jun 2007 14:27:01 +0200 Subject: Re: [help-gengetopt] mutually exclusive group of options > then as soon as I have something ready I'll post it! It means I may except this feature will be included, too: > - check that only one group option has a default > - set the default > - then use only the _given field to check conflicts The check is performed at compile time by gengetopt while the others at runtime by the generated source. This way a default group option (groupdefault?) will behave exactly the same as if it were specified by the user at commandline. Am I right? Btw, default group option resembles to "flag on" a little bit however makes much more sense because to make default one of option from a mutually exlcusive group makes sense ;) I remember now that some gengetopt users were asking in the list how to deal with more than one .ggo files each one defining options of different "subcommands" to the application. If default group option (groupdefault in short) was implemented such subcommands (with their multiple .ggo files) may be converted into a single .ggo file. Not always but sometimes it can be very handy... _______________________________________________ Help-gengetopt mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-gengetopt
_______________________________________________ Help-gengetopt mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-gengetopt
