[cfe-dev] Using C++'11 in llvm/clang itself

[Chris Lattner]

Hi guys,

Please continue this discussion on llvmdev to keep the discussion in one place.

-Chris

On Jan 11, 2013, at 1:13 PM, Joshua Cranmer <pidgeot18 at gmail.com> wrote:

> On 1/11/2013 2:28 PM, dag at cray.com wrote:
>> Matthieu Monrocq <matthieu.monrocq at gmail.com> writes:
>> 
>>> If we move the bar a little higher: gcc 4.6, MSVC 11 (not CRT nov' 12)
>>> and clang 3.1, we add some features.
>>> 
>>> - atomic (n2427) / requires MSVC 11
>>> - forward enum (n2764) / requires gcc 4.6, MSVC 11
>>> - nullptr (n2431) / requires gcc 4.6
>>> - strongly-typed enums (n2347) / requires MSVC 11
>>> - range-based for (n2930) / requires gcc 4.6, MSVC 11
>> >From your extract it looks like MSVC 11 would also add:
>> 
>> - decltype (but for gcc not v1.1 - what is that?)
> MSVC appears to be using it to refer to N3276, which I've briefly looked over to see how it changes decltype. The changes in N3276 amount to dropping the necessity of having intermediates in the expression as a result of function calls being complete types.
>> 
>> And MSVC 11.0v2 (I don't know what that is)
> MSVC released a followup update to MSVC 11 (or 2012) which added more C++11 features; this is generally called the "November CTP".
> 
> -- 
> Joshua Cranmer
> News submodule owner
> DXR coauthor
> 
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev