Re: [boost] arguments parsing, wildcard matcher

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2001-11-16 15:46:57

<opinion><exclaim>Ick<punct>!</punct></exclaim>
<statement><noun>XML</noun> is the opposite of an "easy interface",
even for programmers.</statement></opinion>

Phew! I couldn't even keep it up long enough to tag everything.

----- Original Message -----
From: "Henrik Ravn" <henrik_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Friday, November 16, 2001 11:40 AM
Subject: RE: [boost] arguments parsing, wildcard matcher

> > It occurs to me that even in the simplest cases, the
> > programmer probably needs to write the "usage" output which
> > responds to --help or incorrect options. A truly easy-to-use
> > interface would read and interpret the "usage" text, so that
> > the programmer hardly needs to do anything else. I have no
> > idea how feasible that is...
> Neat idea!
>
> Perhaps it could be done via some form of xml-driven description...
>
> Something along the lines of:
> <cmdline>
> <options>
> <option name="Verbose" match="v,verbose"
> case-sensitive="yes">
> Descriptive text for the usage text goes here
> </option>
> </options>
> <!-- etc etc -->
> </cmdline>
>
> Now, if you just want to parse a few options and a file name, including
> a full xml-parser may well be considered overkill, but perhaps an
> xml->.hpp translation tool could do the trick?
>
> be well
> Henrik
>
>
>
> Info: http://www.boost.org  Unsubscribe:
<mailto:boost-unsubscribe_at_[hidden]>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>