Download this episode
I was able to attend C++ and Beyond 2011 and it was a tremendous experience. The technical depth and C++ goodness was profound and lasted for 3 whole days (and two evenings). Thanks Andrei Alexandrescu, Scott Meyers and Herb Sutter for allowing me to crash your affair with my camera - which was perhaps too big and too advanced for the likes of me - still, I was abe to capture some great content like this panel on C++11 with Scott, Andrei and Herb. Great questions from attendees. Note that this is the first in a series of three panels from C++ and Beyond 2011 that will appear on C9 over the coming months.
Make sure to check out all the C&B 2011 content we're lucky enough to have stored on C9
Table of contents (click on the time code link to move the player to that point in time...):
[00:19] When should new C++11 features be adopted in production?
[09:28] C++11 Memory Model
[15:23] Which C++11 features remain broadly missing?
[16:25] When can we expect full C++11 conformance from the major compilers?
[19:45] -> Herb Sutter asks YOU a question (please answer on this thread): What do you want the standards committee to work on next? Should they immediately start work on new features? Should they take a break before new feature work?
[21:45] What about debugging, linking and tools - as it relates to C++11?
[23:56] What really happened to Concepts?
[29:07] Will existing code have to be changed just to compile with a new C++11 conforming compiler?
[29:38] Why was a seemlingly complicated feature (to implement) like variadic templates rolled out sooner than a seemingly simple feature like templated typedefs?
[32:42] What do you think we'll get wrong most often when using C++11 features?
[45:13] Return by ref or by value - is there a universal rule of thumb?
[48:32] Why don't lambdas have typedefs for argument types?
[53:02] How do you capture enclosing scope variables when using lambdas?
Available formats for this video:
Actual format may change based on video formats available and browser capability.