Boost logo

Boost :

Subject: Re: [boost] [lexical-cast] version of lexical_cast in 1.46.1 is quite older than in trunk
From: Antony Polukhin (antoshkka_at_[hidden])
Date: 2011-04-07 09:13:31


2011/4/7 Vladimir Batov <vbatov_at_[hidden]>:
>> ----- Original Message ----- From: "Vicente BOTET"
>> <vicente.botet_at_[hidden]>
>>>
>>> ... the Convert proposal sitting
>>> in the queue and getting ready for the review this month. I'd suggest
>>> anyone
>>> interested in additional lexical_cast features to have a look the the
>>> proposal
>>> if it already satisfies your needs. If not, then it's most definitely
>>> open for
>>> improvements/extensions/ideas/etc.
>>
>> It will be great to have a performance comparison between your library and
>> lexical cast (with a without the proposed modifications) as one of the
>> major
>> concerns of your library were to provide an interface that performs better
>> than lexical_cast.
>
> As I understand the main goal of the Convert library was to provide richer
> interface (or so I understood). Namely, to support configurable throwing
> behavior, locale, formatting and ability to extend if/when needed.
> Therefore, quite a bit of effort was put into working out the framework, the
> interface. In that light at this stage I feel that trying to address
> performance in Convert would be somewhat premature.

Agreed.

But a lot of libraries (even in boost) use lexical_cast. And
performance improvemnts will be appreciated. Patches only add
performance, and there can be done some more improvements (for float
types conversion). So the quiestion with applying patches is still
open.


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk