|
Boost : |
From: Vladimir Prus (ghost_at_[hidden])
Date: 2001-12-03 08:32:40
David A. Greene wrote:
> > My own personal preference for handling multiple arguments to an
> > option would be to have them enclosed in parentheses, like this:
> >
> > --foo = (bar1 bar2)
> >
> > One could discuss if there should be commas between the arguments
> > within the parentheses (as in the syntax used under VAX/VMS) or not.
> > Personally, I would be just as happy to leave them out: they are not
> > really necessary, and if you leave them out, you open up the
> > possibility to use the command line parser recursively, since
> > the "arg1 arg2 ..." part within the parentheses will look remarkably
> > similar to the "par1 par2 ..." parameters in the command line itself.
>
> Absolutely! As I mentioned earlier on in this thread, I have found
> this sort of thing incredibly useful. It's great for passing
> arguments to plugins, for example.
To tell the truth, I find passing arguments to plugins relatively rare case.
This is the first case I hear about allowed arguments being dynamically
computed, as you tell in another message. Do you think it worth supporting in
a general purpose library?
- Volodya
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk