Herb's last appearance on C9 was a relatively short chat with me about C++0x. You wanted more questions asked and some of you thought I was just too soft on Herb. Well, Herb decided that the best way to get the questions you want asked is, well, to have you ask them. Most of the highest user-rated questions were asked and Herb answers with his usual precision. So, without further ado, it's C++ question and answer time with the great Herb Sutter, powered by you.
Questions (click the question link for Herb's answer):
ZenJu: What is the strategy to deal with C++ language and standard library design flaws in the long run? Are you afraid "bad design decisions" may accumulate over time, thereby making it more and more harder for newbies to learn the language? Herb also briefly discusses noexcept... (two for one!)
Cory: Concepts ? why did they fail and what work is being done to bring something like them back?
Anteru: Modules - Are they really coming, and if so, when do you expect the first implementation?
David: why the long time in C++ standardization work? Will the next standard take as long?
Cory: Filesystem ? something like boost::filesystem is desperately needed.
Cory: Threading ? thread pools, fine-grained task model, thead-safe containers.
Charles: Why not add an async/await language-level pattern to C++ just like in C# vNext?
petke: What is on the top of your post C++0x wishlist?
Thanks for all your great questions and thanks to Herb for taking time out of his insanely busy schedule to sit down and answer as many of the highly user-rated questions as possible. Great stuff! We should do this again. For all the folks who asked about specific VC vNext implementations, please try to make it to BUILD as there will be a significant C++ presence at the developer affair in Anaheim (Sept 13-16, 2011). If you can't attend the event in person, then you will be able to watch all of the session online, as usual, after the event right here on Channel 9.
MICROSOFT MICROSEMI MICROS SYSTEMS MICRON TECHNOLOGY MICROCHIP TECHNOLOGY
No comments:
Post a Comment