Re: [boost] [Config] Big changes in C++0x detection...

Subject: Re: [boost] [Config] Big changes in C++0x detection...
From: Noah Roberts (roberts.noah_at_[hidden])
Date: 2011-03-16 16:38:40

On 3/16/2011 12:45 PM, Mathias Gaunard wrote:
> On 16/03/2011 19:39, John Maddock wrote:
>>>> * Remove the concept related macros.
>>>> * Tighten up most of the C++0x related tests, with the result that some
>>>> C++0x features that were previously enabled are no longer - this may
>>>> also cause the Boost.Config tests to fail on some platforms.
>>>> * Some C++0x features that were not previously enabled are now -
>>>> because
>>>> they were passing the Boost.Config tests - there's at least one case
>>>> where this is causing regressions in other libraries - if any more pop
>>>> up please let me know ASAP!
>>>
>>> Any reason why decltype on MSVC10 is still not enabled?
>>
>> If someone tells me that this issue:
>> http://lists.boost.org/Archives/boost/2010/04/164645.php is fixed then
>> fine, otherwise it appears to be a lot trouble,
>
> I wasn't aware of this issue.
> But doesn't it only affect result_of, with decltype still usable in
> practice for other things?

Some.  The VS2010 compiler's decltype implementation gets a lot of 
things wrong though.  It'll result in "T const" rather than "T" when 
used in auto returns and it gets function types wrong.  I can't at the 
moment immediately think of the exact reproduction steps but I do know 
that decltype as implemented by 2010 is pretty far from being compliant. 
  I still use it but every once in a while run into its issues.