[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] Re: boost::program_options
From: |
Corey Halpin |
Subject: |
Re: [Monotone-devel] Re: boost::program_options |
Date: |
Tue, 19 Apr 2005 15:21:14 -0500 |
User-agent: |
Mutt/1.4.1i |
On 2005-04-19, Richard Levitte - VMS Whacker wrote:
> In message <address@hidden> on Sat, 2 Apr 2005 15:39:03 -0800, Nathaniel
> Smith <address@hidden> said:
>
> Uhmmm... Eeep! From a technological point of view, this may head us
> toward hell. Basically, it would entail accepting all possible
> options, then check the subcommand and see if any of the options we
> just accepted should really be rejected.
This might be hitting a little nail with a big hammer, but has anyone
considered writing a flex/yacc parser/scanner, and then just parsing command
options with yy_scan_string() ?
I know it can provide subcommand support. :-)
I don't have any idea where the option parsing code is in monotone, and I
don't know my way around popt, so just sending in a patch isn't something I
can do. But if someone more clueful were to tell me what is desired, I'd
be glad to help.
crh
- Re: [Monotone-devel] popt buggy, (continued)
- Re: [Monotone-devel] popt buggy, Julio M. Merino Vidal, 2005/04/02
- boost::program_options (was Re: [Monotone-devel] popt buggy), Nathaniel Smith, 2005/04/02
- Re: boost::program_options (was Re: [Monotone-devel] popt buggy), Vladimir Prus, 2005/04/04
- Re: boost::program_options (was Re: [Monotone-devel] popt buggy), Jon Bright, 2005/04/05
- Re: boost::program_options (was Re: [Monotone-devel] popt buggy), Vladimir Prus, 2005/04/05
- [Monotone-devel] Re: boost::program_options, Richard Levitte - VMS Whacker, 2005/04/19
- Re: [Monotone-devel] Re: boost::program_options,
Corey Halpin <=
- Re: [Monotone-devel] popt buggy, Richard Levitte - VMS Whacker, 2005/04/04
Re: [Monotone-devel] popt buggy, Richard Levitte - VMS Whacker, 2005/04/02
Re: [Monotone-devel] popt buggy, Richard Levitte - VMS Whacker, 2005/04/02