News for hackers. Stuff that matters.
Re:Visual C++ 2015 Brings Modern C++ to the Windows API by CyberDildonics on Saturday January 03, 2015 @07:54PM (#8832720)
Will 2015 be the year Microsoft fully supports C++11?
Re:Visual C++ 2015 Brings Modern C++ to the Windows API by plorkyeran on Saturday January 03, 2015 @10:46PM (#8833196)
Close enough for most people, but no. Based on their latest update[0], at the minimum it'll be missing attribute expression SFINAE, an unfucked preprocessor, and unfucked (C++98) template name lookup. If you're feeling charitable the latter two could be called bugs rather than missing features (and bugs that will break a bunch of existing code when they're fixed).

[0] https://view.officeapps.live.com/op/view.aspx?src=http%3a%2f...

Re:Visual C++ 2015 Brings Modern C++ to the Windows API by pjmlp on Sunday January 04, 2015 @02:51AM (#8833787)
Will 2015 be the year other commercial C++ vendors (Intel, Borland, Green Hills, CodePlay HP, IBM, Oracle,...) catch up Microsoft?
Re:Visual C++ 2015 Brings Modern C++ to the Windows API by cokernel_hacker on Sunday January 04, 2015 @04:58AM (#8833978)
No, that was probably 2014.

Intel ships a compiler based on Clang: http://llvm.org/devmtg/2014-04/PDFs/Posters/ClangIntel.pdf

This means they get clang's ridiculously conforming implementation with icc's performance.

Re:Visual C++ 2015 Brings Modern C++ to the Windows API by pjmlp on Sunday January 04, 2015 @11:52AM (#8834941)
Unless Intel's documentation is out of date, they still haven't full C++11 support.

https://software.intel.com/en-us/articles/c0x-features-suppo...

Re:Visual C++ 2015 Brings Modern C++ to the Windows API by cokernel_hacker on Monday January 05, 2015 @01:46AM (#8837640)
Those docs refer to Intel Composer XE 2013. The PDF I linked to is with regards to Intel Composer XE 2015.
Re:Visual C++ 2015 Brings Modern C++ to the Windows API by pjmlp on Monday January 05, 2015 @03:21AM (#8837852)
Have you bothered to read the "Version 15.0" column at all?