$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
From: Jody Hagins (jody-boost-011304_at_[hidden])
Date: 2004-11-24 11:46:31
On Wed, 24 Nov 2004 19:01:54 +0300
Vladimir Prus <ghost_at_[hidden]> wrote:
> > 1. Ability to tell the parser to be in "strict" mode or something
> > like that, where it assumes options come first, and "positional
> > options" follow.  This will remove all ambiguity in parsing options,
> > and AFAIK, it is consistent with just about all conventions.
> 
> As I mention above, I'm not sure this is right approach.
Even as an option that the user must set on the cmdline parser?
> What about 
> 
>    program --something 10 11 --known_option
> 
> In this case, after parsing know options you'll get 
> 
>   --something 10 11
> 
> which can be passed to another parser, which will eat 
>   
>   --something 10
> 
> and will leave one token, which will be considered positional options.
> Seems OK.
Seems OK at first blush.  Like everything though, someone will come
along later with something we have not considered...