Subject: Re: [boost] Is there any interest in command line interpreter class templates?
From: alexey.tsoy (tsoy.alexey_at_[hidden])
Date: 2011-06-22 18:00:42
| One of the primary reasons that I (and others) avoid
| that it doesn't 'natively' support wide strings (wide strings are
| static_cast to narrow strings with no regard to localization or
| internationalization). How does this library compare in that
This library was developed with taking an account of variable string
Here is explanation how it is dealt with wide strings below.
The class interpreter<CharType, .. > has invoke() function template.
Executing the function
cause to calling appropriate handler like below
type_cast <first_argument_type> (*
, type_cast <second_argument_type> (*
With this you can be sure that during intervening calls,
the data will not be changed.
Also in the class there is a template function "visit". By passing your
'visitor' into the function you can get information about all registered
their alternative names and description.
Display the information based on internationalization settings.
One more moment that may be will have to reconsider it is parser
which is present in library. I have tested it to wstring, however, it can
not be working in some situations. But in any case, you have the ability
use your own parser.
| How does it compare to program_options in term of features, test and new
| Enabled use cases?
To the features can be attributed automatically detecting parameters of
an option(on the basis of the signature handler).
That allows us to develop more reliable code.
Auto-tests of multiple base classes are available.
Thank you very much for your interest.
P.S. please give my apologies for long reply due to my poor English.
-- View this message in context: http://boost.2283326.n4.nabble.com/Is-there-any-interest-in-command-line-interpreter-class-templates-tp3612663p3618390.html Sent from the Boost - Dev mailing list archive at Nabble.com.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk