Re: [boost] [config][clang] Does <boost/config/compiler/clang.hpp> need updating?

Subject: Re: [boost] [config][clang] Does <boost/config/compiler/clang.hpp> need updating?
From: Doug Gregor (doug.gregor_at_[hidden])
Date: 2011-02-05 15:43:46

On Sat, Feb 5, 2011 at 12:41 PM, Christopher Jefferson
<chris_at_[hidden]> wrote:
>
> On 5 Feb 2011, at 19:46, Bryce Lelbach (wash) wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On Sat, 5 Feb 2011 10:26:20 -0800
>> Doug Gregor <doug.gregor_at_[hidden]> wrote:
>>
>>> Clang itself is just now getting some C++0x support. It has rvalue
>>> references, variadic templates, decltype, static_assert, and some
>>> other goodies. We think it's in decent shape, but obviously we need
>>> more testing coverage.
>>
>> On Darwin. On Linux, clang C++0x support is a moot point because clang-linux
>> uses the GNU stdlib. Also, according to the regression tests, clang + libc++
>> can't compile most of Boost.
>
> I started those tests just a day ago. I managed to mess up both the user-config.jam, and stopping the results getting submitted to the official boost test page. Hopefully more reasonable tests should appear in the next couple of days.

Great!

> Out of interest, how should I best add c++0x to clang? At the moment, I am just passing -std=c++0x as a compileflag.

You might want to use -std=gnu++0x, to enable GNU extensions. That's
the same recommendation one usually sees for C++0x in GCC.

How is this handled in Boost.Build? Is there some global C++0x feature
that we should be hooking into?

  - Doug