News for hackers. Stuff that matters.
Re:The Sorry State of C++ Portability by munin on Wednesday October 24, 2012 @03:31PM (#4694620)
"Perhaps by 2014 or so, Microsoft will have overcome their intellectual challenges..."

was this really necessary? I'm quite sure that Microsoft is smart enough to implement the C++11 standard, so why it isn't implemented is actually more nuanced than "they're dumb lol". Could it be that you're one of a very small minority who would run into these problems?

Re:The Sorry State of C++ Portability by fafner on Wednesday October 24, 2012 @05:05PM (#4695053)
Yes it is necessary. Microsoft has people like Herb Sutter talking about how awesome C++11 is and that Microsoft is totally committed to it. But then they support barely anything of C++11. They are the once holding back the adoption. GCC and Clang support all the core features.

Of course the people working on VC++ aren't dumb. But Microsoft is apparently not investing enough money. So it's absolutely necessary to call them out.

Re:The Sorry State of C++ Portability by eridius on Wednesday October 24, 2012 @03:54PM (#4694730)
From the context, that seems to be a reaction to "variadic templates are too hard for us to implement" (paraphrased).
Re:The Sorry State of C++ Portability by Locke1689 on Thursday October 25, 2012 @03:14PM (#4699031)
That's not what Herb Sutter said. If you watch the video, he said they just barely missed making the deadline for VS2012 and it would be available soon after.
Re:The Sorry State of C++ Portability by webreac on Wednesday October 24, 2012 @03:57PM (#4694743)
I was developing programs for HPUX and visual studio between 1999 and 2002. I was such a pain that I have done my best (with success) to never code again in this language. By their very poor support of C++, I think that they have contributed a lot to the success of java.
Re:The Sorry State of C++ Portability by pjmlp on Thursday October 25, 2012 @05:49PM (#4699732)
This was actually a reason for Java's success in the enterprise.

Finally a OO language with proper use of Strings, exceptions, classes and available library, without having to litter your code with #ifdefs to manage portability across compiler vendors and operating systems.

Or reducing yourself to the common subset usually available, which has a bit hard to have across C and C++ compilers around 1996.

Nowadays we know better, but it was surely a reason among many others, for Java's success.

I state this, because I saw it happen live in the trenches back in the day.