tags:

views:

378

answers:

3

We've been waiting forever to see if it's going to become a full-fledged language, and yet there doesn't seem to be a release of the formal definition. Just committees and discussions and revising.

Does anyone know of a planned deadline for C++0x, or are we going to have to start calling it C++1x?

+13  A: 

Well the committee is currently very busy working on the next revision - every meeting is prefaced by many papers, that are a good indicator of the effort that is going into the new standard: http://www.open-std.org/jtc1/sc22/wg21/

What is a little concerning (but reassuring in the sense that they will not rush publishing a standard just to assuage the public, yet do sense the urgency involved) is that Stroustrup just put out a paper saying that we need to take a second look at concepts and make sure that they are as simple as can be - and has proposed a reasonable solution. [Edit] For those who are interested, this paper is available at: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2009/n2906.pdf.

C++0x will be a huge improvement upon C++ in many regards, and while I do not speak for the committee - my hope is that it will happen by late 2010.

[Edit] As underscored by one of the commenters, it is worth appreciating that there is significant concern amongst a few committee members that either the quality of the standard or the schedule (late 2010) will have to suffer if concepts are included: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2009/n2893.pdf. But whether these concerns will be substantiated is worth being patient about - we will have more information about this once the committee concludes its meeting in Frankfurt this july (the post-meeting mailing can be expected in late-july, early august).

Personally, i sense that it would not be a huge loss to get the standard out without concepts (maintain the late 2010 schedule), and then add them as a TR - versus rushing them through even when there is palpable uneasiness amongst the more seasoned committee members (about concepts) - but I will defer to the committee here - while they have never claimed or been described as perfect, the majority of them are far more qualified to make these decisions than I am and deserve some of our confidence if history is any indicator - I would err on the side of trusting their instincts (over mine) assuming there was some reasonable consensus amongst them.

For some perspective, and so that one does not despair about these obstacles too much, compare this to what happened within the ecmascript community - Brendan Eich, the creator, had some very different design goals for the next revision of ecmascript (es5) from some of the other similarly talented wizards in the ecmascript community - they had multiple meetings and after much discussion (some of it heated ;) formulated a very very reasonable compromise followed by a frenzy of activity that has resulted in ecmascript 5 (all in the span of 1-2 years, including the conflict) which will be an excellent and pragmatic, yet much more conservative than Eich had initially proposed, revision of javascript. I have similar hopes for C++ (acknowledging that C++ is a much much much larger language - but then much more effort has been put in ;)

Faisal Vali
concepts seem to be the show-stopper currently :( This is an interesting paper about the issue: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2009/n2893.pdf the long pole gets longer :(
Johannes Schaub - litb
yes - the issue with concepts is definitely concerning - but i think good will come from it - even if they don't deliver it in the next version of the C++ standard, with 3-5 year cycles, we'll get to play with them soon enough ;)
Faisal Vali
Here's the paper I assume Faisal was referring to: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2009/n2906.pdf - I just read it, interesting stuff, but it also made me a lot more skeptical about the idea of concepts. It seems like unless they're extremely careful, it could pretty much destroy generic programming, or at least bring the standard badly out of sync with actual users of the language.
jalf
I wish they would pull concepts and ship. There are other features which I feel are just as important: new memory model, auto, lambdas, variadic templates. I think each of these individually will help "average" users more than concepts every will. Shipping a smaller standard also means that compilers have a achievable target std now. This will hopefully reduce the chance of what happend to C++98 where it took 10 years before you could use 99% of C++ features more or less in a portable way.
Richard Corden
The next meeting is in frankfurt next month. Let's build up a SO-group and demonstrate "concepts out!" there =)
Johannes Schaub - litb
heh heh - i'm all about standing up against power structures gone wrong - but i'd like to give the committee some space here (at least initially ;) - i find stroustrup (based on his writings) to be a mostly pragmatic person - and I have reasonable confidence in some of the other wizards (based on their books, and writings too) who attend those meetings - so i'm holding on to hope (how ever misplaced the rest of you may think it might be ;)
Faisal Vali
Count me in as another vote for dropping concepts. They're so huge, it's almost like adding C++/CLI (okay, maybe not that huge).
Daniel Earwicker
A: 

Around 200A or 200B. If you remember the Y2K problem, these are years 199K and 199L ... oops wait, K and L aren't hex digits. Boom!

Windows programmer
A: 

Slashdot posted a story of an interview with Bjarne Stroustrup, and in it, he drops the bombsheel that the release has been delayed until 2010 or later:

No C++0x, Long Live C++1x (Page 3)!

Kieveli