On 11/10/2010 22:08, Marsh Ray wrote:
On 10/11/2010 01:23 PM, Mathias Gaunard wrote:
I think the important question is the following:
Do we care about C++ locales support in lexical_cast?
Not I. If I could get std::string and std::stream without locales, I'd use them. (Even better might be an STL without allocators, but that's a different question.)
Are people fine scrapping lexical_cast and have construe_cast take its name?
I'm not a heavy user of lexical_cast, but want to echo the concern about a potential increase in build times.
I attempted a small project with Spirit once and the compile time was noticeable. While it was acceptable for a translation unit producing a high-tech parser, I wouldn't want that overhead creeping into everything through some seemingly innocuous string conversion functions.
I suppose it would be less of a problem if precompiled headers usage was generalized. The template definition could be exported, too, preventing the instantiations altogether.