On 17 November 2012 15:25, Vicente J. Botet Escriba <vicente.botet@wanadoo.fr> wrote:
Le 17/11/12 15:52, Daniel James a écrit :
This is only an issue with older versions of libstdc++ in C++11 mode, so I don't think it's a common problem. I only came across it in Boost.Test because I was trying to recreate an error people were seeing. For normal development, I'd never do it.
So IIUC, the config clang + -std=c++0x/c++11 + gcc non c++11 supporting library is not a usual case, and so should not be supported.
No, I just don't think it's common, so it isn't essential. But it's certainly nice to support it - I do. I don't have any real data on how common it is, and the same issue might pop up elsewhere, so it's hard to tell just how important it is, or isn't.
Every time I've installed clang on MacOs it uses a standard library non-supporting c++11. I though that was a know issue.
Yes, I mentioned that in another mail. Apple doesn't support gcc versions after 4.2, so the default libstdc++ is an old one. I just imagine that anyone who wants to use clang for c++11 development on a mac with Snow Leopard or later will install libc++, or just use a recent g++.