Re: [help-gengetopt] gengetopt open issues

[Andre Noll]

Hi Lorenzo,

First of all, it's great news to hear that you found the time to work
on gengetopt development again.

On Wed, Sep 14, 10:27, Lorenzo Bettini wrote:
> Thus, I think we should use the tool at savannah to keep track of
> issues;

I don't think this is a good idea. If something was lost in your inbox,
people will eventually send it again, at least if it is important
enough to them ;)

OTOH, bug trackers and ticket systems, like Wikis, tend to be "write
only", i.e. nobody ever reads what other people wrote there before
posting a bug report or feature request. Moreover there are people,
including myself, who hate mousing around and learning how to use yet
another "user-friendly" web-based system including its word-like web
editor. Having to register before you can post is another barrier.

That being said, here's what I am missing most in gengetopt:

* A new ggo option that works just like "text" but adds the text only
  to the output of --detailed-help and not to the short --help output.

* Support for environment variables for the defaults of string options.
  For example, the default location of a file might be inside the
  user's home directory. So it would be nice if one could specify
  the default value for a string option as "$HOME/.foorc" in the ggo
  file. Of course $HOME has to be evaluated when the program runs
  (rather than when gengetopt is executed).

* Ranges. At least for int type options it would be nice to be able
  to specify that the value of the given option must be in some
  interval. In particular, gengetopt could generate code that checks
  whether the given integer is positive.

* Including ggo files from other ggo files. This is the least important
  point, as one can easily do this manually, e.g. with m4.

Regards
Andre
-- 
The only person who always got his work done by Friday was Robinson Crusoe

signature.asc
Description: Digital signature