Linked by Thom Holwerda on Sun 29th Jan 2006 16:06 UTC, submitted by Derek Jones
Permalink for comment 90701
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2005-09-01
That's OK. The whole fuss is about not calling the new language so it can be confused with real C++ a it's not much closer (given its intended usage practices) to C++ than to say C#.
The document explained why the confusion (which MS actually intentionally spurs) is hurtfull to C++ and beneficial to MS.
Besides some features in the language are syntactic sugar which are to lure C++ developers from the standard.
Generally it's interesting if there're means to stop MS from calling their hibrid languages what they aren't.