Boost C++ Libraries: Ticket #5406: Incorrection assumption of Intel C++ Composer for Windows behaviour for c++0x features https://svn.boost.org/trac10/ticket/5406 <p> I have confirmed with Intel the behaviour of C++ Composer XE's behaviour with respect to how it manages C++0x features it supports which VS 2010 SP1 doesn't support. You can read about it here: <a class="ext-link" href="http://software.intel.com/en-us/forums/showthread.php?t=81434&amp;p=1#144607"><span class="icon">​</span>http://software.intel.com/en-us/forums/showthread.php?t=81434&amp;p=1#144607</a> </p> <p> In a nutshell, Intel partially supports strongly typed enums while Microsoft doesn't (at least not c++0x syntax). However in boost/config/compiler/intel.hpp, it assumes that Intel and MS supports the exact same c++0x language features. </p> <p> I have just checked the trunk, and the line indicating support for scoped enums (L212) has been commented out. However, boost can compile correctly if /Qstd=c++0x is specified and that line is not commented. It might be a small thing, but it is good if this can be fixed. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/5406 Trac 1.4.3 John Maddock Mon, 25 Apr 2011 09:35:37 GMT status changed; resolution set https://svn.boost.org/trac10/ticket/5406#comment:1 https://svn.boost.org/trac10/ticket/5406#comment:1 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">wontfix</span> </li> </ul> <p> I belive it's deliberately disabled, Intel's support for scoped enums is officially described as "partial": <a class="ext-link" href="http://software.intel.com/en-us/articles/c0x-features-supported-by-intel-c-compiler/"><span class="icon">​</span>http://software.intel.com/en-us/articles/c0x-features-supported-by-intel-c-compiler/</a> </p> <p> And I believe it did actually break stuff when that line was briefly enabled, so for now it stays disabled. Sorry! </p> Ticket Edward Rankin <erankin@…> Thu, 28 Apr 2011 08:22:33 GMT <link>https://svn.boost.org/trac10/ticket/5406#comment:2 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/5406#comment:2</guid> <description> <p> I guess my main point for posting this ticket is that C++0x language support differs between VC++ and Intel C++, but the structure of the header file cannot support such differences. </p> <p> A good example is nullptr support. If boost starts using nullptr, VC++ supports that keyword but not Intel C++. </p> <p> That's why my ticket title is not about scoped enum but about the assumption made in the logic of deciding what C++0x features the compiler supports. </p> </description> <category>Ticket</category> </item> </channel> </rss>