$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
Subject: Re: [boost] Formal Review Request: Boost.String.Convert
From: Hartmut Kaiser (hartmut.kaiser_at_[hidden])
Date: 2009-02-16 21:18:39
> Upgraded to the version 0.10. Added boost::string::is_string<T>
> SFINAE-based check. That allowed to discriminate the applicability of
> conversion functions. Now they demand one of the parameters to be a
> string
> (in broad sense, like C strings, std::(w)string, chat/wchar_t-based
> containers) and the other *not* a string. Have straighten up the main
> boost::string::convert() interface (was quite broken) so that all the
> tests now run as expected.
Why not allow to convert between different string types?
Possible applications:
- std::string <--> std::wstring or similar (based on a future
Boost.Unicode library)
- conversion between different symbol (character) sets
Regards Hartmut