Le 10/10/12 10:24, Daniel James a écrit :
Okay. I've only checked in the changes that are already in the beta, I'll deal with the others later, I need to somehow make it clear that
On 10 October 2012 00:06, Vicente J. Botet Escriba <vicente.botet@wanadoo.fr> wrote: they're not in the actual beta.
Btw. IMO you shouldn't require the user to define macros just to be able to compile the library, is u32string support really that important?
Well, support for u16string and u32 string has been delivered long time ago, so removing them seems not an alternative, or is it? Then I'd put some sort of special case for the problematic standard library myself, but if you feel that's not worth it, then it's your decision.
Oh, I see. Instead of using the future BOOST_NO_CXX11_U16STRING I can use my own macro that is defined when compiling with the already identified library. I will made the update as soon as possible hopping it could go to the release. Thanks, Vicente