Re: [boost] Formal Review Request: Boost.Convert

Subject: Re: [boost] Formal Review Request: Boost.Convert
From: David Abrahams (dave_at_[hidden])
Date: 2009-02-22 12:42:22

on Sun Feb 22 2009, "Vladimir Batov" <batov-AT-people.net.au> wrote:

>>> I looked a Boost.Parameter and will certainly try using it somewhere. My hesitation
>>> with it for boost::convert is I am under impression that the set of acceptable
>>> parameters (radix_, etc.) has to be predefined and therefore cannot be extended by
>>> the user when formatting like "convert(str) >> std::hex" seems more flexible.
>>
>> You can add new keywords as needed.
>
> Where can I add those "new keywords" to? If it is into convert(),  then I do not feel
> it is appropriate as for every user "needed" will be different and I cannot see
> convert() collecting *all* those "needed" keywords from every user on the globe.

The keywords are decoupled.

>> The point is that the underlying conversion mechanism can support a subset of these
>> keywords, specific to the conversion domain. This way it will be a non-intrusive
>> extension.
>
> I cannot understand how it can be a "non-intrusive extension" if every new keyword
> needs to be stored/registered *inside* convert<string, int>... 

Did you read through the Boost.Parameter tutorial? 

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com