Channel 9 - Entries tagged with C++ and Beyond 2012 Microsoft http://mschnlnine.vo.llnwd.net/d1/Dev/App_Themes/C9/images/feedimage.png Channel 9 - Entries tagged with C++ and Beyond 2012 http://channel9.msdn.com/Tags/cppbeyond+2012 Channel 9 keeps you up to date with the latest news and behind the scenes info from Microsoft that developers love to keep up with. From LINQ to SilverLight – Watch videos and hear about all the cool technologies coming and the people behind them. http://channel9.msdn.com/Tags/cppbeyond+2012 en Sat, 18 May 2013 23:15:04 GMT Sat, 18 May 2013 23:15:04 GMT Rev9 9 1 25 C++ and Beyond 2012: Herb Sutter - atomic&lt;&gt; Weapons, 2 of 2 Herb Sutter presents atomic<> Weapons, 2 of 2. This was filmed at C++ and Beyond 2012. As the title suggests, this is a two part series (given the depth of treatment and complexity of the subject matter).

STOP! => Watch part 1 first!

Download the slides.

Abstract:

This session in one word: Deep.

It's a session that includes topics I've publicly said for years is Stuff You Shouldn't Need To Know and I Just Won't Teach, but it's becoming achingly clear that people do need to know about it. Achingly, heartbreakingly clear, because some hardware incents you to pull out the big guns to achieve top performance, and C++ programmers just are so addicted to full performance that they'll reach for the big red levers with the flashing warning lights. Since we can't keep people from pulling the big red levers, we'd better document the A to Z of what the levers actually do, so that people don't SCRAM unless they really, really, really meant to.

Topics Covered:

  • The facts: The C++11 memory model and what it requires you to do to make sure your code is correct and stays correct. We'll include clear answers to several FAQs: "how do the compiler and hardware cooperate to remember how to respect these rules?", "what is a race condition?", and the ageless one-hand-clapping question "how is a race condition like a debugger?"
  • The tools: The deep interrelationships and fundamental tradeoffs among mutexes, atomics, and fences/barriers. I'll try to convince you why standalone memory barriers are bad, and why barriers should always be associated with a specific load or store.
  • The unspeakables: I'll grudgingly and reluctantly talk about the Thing I Said I'd Never Teach That Programmers Should Never Need To Now: relaxed atomics. Don't use them! If you can avoid it. But here's what you need to know, even though it would be nice if you didn't need to know it.
  • The rapidly-changing hardware reality: How locks and atomics map to hardware instructions on ARM and x86/x64, and throw in POWER and Itanium for good measure – and I'll cover how and why the answers are actually different last year and this year, and how they will likely be different again a few years from now. We'll cover how the latest CPU and GPU hardware memory models are rapidly evolving, and how this directly affects C++ programmers.
]]> http://channel9.msdn.com/Shows/Going+Deep/Cpp-and-Beyond-2012-Herb-Sutter-atomic-Weapons-2-of-2 Herb Sutter presents atomic&lt;&gt; Weapons, 2 of 2. This was filmed at C&#43;&#43; and Beyond 2012. As the title suggests, this is a two part series (given the depth of treatment and complexity of the subject matter). STOP! =&gt; Watch part 1 first! Download the slides. Abstract: This session in one word: Deep. It's a session that includes topics I've publicly said for years is Stuff You Shouldn't Need To Know and I Just Won't Teach, but it's becoming achingly clear that people do need to know about it. Achingly, heartbreakingly clear, because some hardware incents you to pull out the big guns to achieve top performance, and C&#43;&#43; programmers just are so addicted to full performance that they'll reach for the big red levers with the flashing warning lights. Since we can't keep people from pulling the big red levers, we'd better document the A to Z of what the levers actually do, so that people don't SCRAM unless they really, really, really meant to. Topics Covered: The facts: The C&#43;&#43;11 memory model and what it requires you to do to make sure your code is correct and stays correct. We'll include clear answers to several FAQs: &quot;how do the compiler and hardware cooperate to remember how to respect these rules?&quot;, &quot;what is a race condition?&quot;, and the ageless one-hand-clapping question &quot;how is a race condition like a debugger?&quot; The tools: The deep interrelationships and fundamental tradeoffs among mutexes, atomics, and fences/barriers. I'll try to convince you why standalone memory barriers are bad, and why barriers should always be associated with a specific load or store. The unspeakables: I'll grudgingly and reluctantly talk about the Thing I Said I'd Never Teach That Programmers Should Never Need To Now: relaxed atomics. Don't use them! If you can avoid it. But here's what you need to know, even though it would be nice if you didn't need to know it. The rapidly-changing hardware reality: How locks and atomics map to hardwar 5553 http://channel9.msdn.com/Shows/Going+Deep/Cpp-and-Beyond-2012-Herb-Sutter-atomic-Weapons-2-of-2 Mon, 11 Feb 2013 16:30:35 GMT http://channel9.msdn.com/Shows/Going+Deep/Cpp-and-Beyond-2012-Herb-Sutter-atomic-Weapons-2-of-2 Charles Charles 15 http://channel9.msdn.com/Shows/Going+Deep/Cpp-and-Beyond-2012-Herb-Sutter-atomic-Weapons-2-of-2/RSS C++ Programming Memory Herb Sutter C++11 C++ and Beyond 2012 C++ and Beyond 2012: Herb Sutter - atomic&lt;&gt; Weapons, 1 of 2 Herb Sutter presents atomic<> Weapons, 1 of 2. This was filmed at C++ and Beyond 2012. As the title suggests, this is a two part series (given the depth of treatment and complexity of the subject matter).

Part 1 -> Optimizations, races, and the memory model; acquire and release ordering; mutexes vs. atomics vs. fences

Download the slides.

Abstract:

This session in one word: Deep.

It's a session that includes topics I've publicly said for years is Stuff You Shouldn't Need To Know and I Just Won't Teach, but it's becoming achingly clear that people do need to know about it. Achingly, heartbreakingly clear, because some hardware incents you to pull out the big guns to achieve top performance, and C++ programmers just are so addicted to full performance that they'll reach for the big red levers with the flashing warning lights. Since we can't keep people from pulling the big red levers, we'd better document the A to Z of what the levers actually do, so that people don't SCRAM unless they really, really, really meant to.

Topics Covered:

  • The facts: The C++11 memory model and what it requires you to do to make sure your code is correct and stays correct. We'll include clear answers to several FAQs: "how do the compiler and hardware cooperate to remember how to respect these rules?", "what is a race condition?", and the ageless one-hand-clapping question "how is a race condition like a debugger?"
  • The tools: The deep interrelationships and fundamental tradeoffs among mutexes, atomics, and fences/barriers. I'll try to convince you why standalone memory barriers are bad, and why barriers should always be associated with a specific load or store.
  • The unspeakables: I'll grudgingly and reluctantly talk about the Thing I Said I'd Never Teach That Programmers Should Never Need To Now: relaxed atomics. Don't use them! If you can avoid it. But here's what you need to know, even though it would be nice if you didn't need to know it.
  • The rapidly-changing hardware reality: How locks and atomics map to hardware instructions on ARM and x86/x64, and throw in POWER and Itanium for good measure – and I'll cover how and why the answers are actually different last year and this year, and how they will likely be different again a few years from now. We'll cover how the latest CPU and GPU hardware memory models are rapidly evolving, and how this directly affects C++ programmers.

Part 2 -> Restrictions on compilers and hardware (incl. common bugs); code generation and performance on x86/x64, IA64, POWER, ARM, and more; relaxed atomics; volatile

]]> http://channel9.msdn.com/Shows/Going+Deep/Cpp-and-Beyond-2012-Herb-Sutter-atomic-Weapons-1-of-2 Herb Sutter presents atomic&lt;&gt; Weapons, 1 of 2. This was filmed at C&#43;&#43; and Beyond 2012. As the title suggests, this is a two part series (given the depth of treatment and complexity of the subject matter). Part&nbsp;1 -&gt;&nbsp;Optimizations, races, and the memory model; acquire and release ordering; mutexes vs. atomics vs. fences Download the slides. Abstract: This session in one word: Deep. It's a session that includes topics I've publicly said for years is Stuff You Shouldn't Need To Know and I Just Won't Teach, but it's becoming achingly clear that people do need to know about it. Achingly, heartbreakingly clear, because some hardware incents you to pull out the big guns to achieve top performance, and C&#43;&#43; programmers just are so addicted to full performance that they'll reach for the big red levers with the flashing warning lights. Since we can't keep people from pulling the big red levers, we'd better document the A to Z of what the levers actually do, so that people don't SCRAM unless they really, really, really meant to. Topics Covered: The facts: The C&#43;&#43;11 memory model and what it requires you to do to make sure your code is correct and stays correct. We'll include clear answers to several FAQs: &quot;how do the compiler and hardware cooperate to remember how to respect these rules?&quot;, &quot;what is a race condition?&quot;, and the ageless one-hand-clapping question &quot;how is a race condition like a debugger?&quot; The tools: The deep interrelationships and fundamental tradeoffs among mutexes, atomics, and fences/barriers. I'll try to convince you why standalone memory barriers are bad, and why barriers should always be associated with a specific load or store. The unspeakables: I'll grudgingly and reluctantly talk about the Thing I Said I'd Never Teach That Programmers Should Never Need To Now: relaxed atomics. Don't use them! If you can avoid it. But here's what you need to know, even though it would be nice if you did 4872 http://channel9.msdn.com/Shows/Going+Deep/Cpp-and-Beyond-2012-Herb-Sutter-atomic-Weapons-1-of-2 Mon, 11 Feb 2013 16:30:10 GMT http://channel9.msdn.com/Shows/Going+Deep/Cpp-and-Beyond-2012-Herb-Sutter-atomic-Weapons-1-of-2 Charles Charles 11 http://channel9.msdn.com/Shows/Going+Deep/Cpp-and-Beyond-2012-Herb-Sutter-atomic-Weapons-1-of-2/RSS C++ Programming Memory Herb Sutter C++11 C++ and Beyond 2012 C++ and Beyond 2012: Herb Sutter - C++ Concurrency Herb Sutter presents C++ Concurrency. This was filmed at C++ and Beyond 2012.

Get Herb's slides for this session.

Herb says:

I've spoken and written on these topics before. Here's what's different about this talk:

  • Brand new: This material goes beyond what I've written and taught about before in my Effective Concurrency articles and courses.
  • Cutting-edge current: It covers the best-practices state of the art techniques and shipping tools, and what parts of that are standardized in C++11 already (the answer to that one may surprise you!) and what's en route to near-term standardization and why, with coverage of the latest discussions.
  • Blocking vs. non-blocking: What's the difference between blocking and non-blocking styles, why on earth would you care, which kinds does C++11 support, and how are we looking at rounding it out in C++1y?

The answers all matter to you – even the ones not yet in the C++ standard – because they are real, available in shipping products, and affect how you design your software today.

]]> http://channel9.msdn.com/Shows/Going+Deep/C-and-Beyond-2012-Herb-Sutter-Concurrency-and-Parallelism Herb Sutter presents C&#43;&#43; Concurrency. This was filmed at C&#43;&#43; and Beyond 2012. Get Herb's slides for this session. Herb says: I've spoken and written on these topics before. Here's what's different about this talk: Brand new:&nbsp;This material goes beyond what I've written and taught about before in my Effective Concurrency articles and courses. Cutting-edge current:&nbsp;It covers the best-practices state of the art&nbsp;techniques and&nbsp;shipping tools, and what parts of that are standardized&nbsp;in C&#43;&#43;11 already (the answer to that one may surprise you!) and what's en route to&nbsp;near-term standardization&nbsp;and why, with coverage of the latest discussions. Blocking vs. non-blocking:&nbsp;What's the difference between blocking and non-blocking styles, why on earth would you care, which kinds does C&#43;&#43;11 support, and how are we looking at rounding it out in C&#43;&#43;1y? The answers all matter to you – even the ones not yet in the C&#43;&#43; standard – because they are real, available in shipping products, and affect how you design your software today. 4538 http://channel9.msdn.com/Shows/Going+Deep/C-and-Beyond-2012-Herb-Sutter-Concurrency-and-Parallelism Fri, 04 Jan 2013 15:42:32 GMT http://channel9.msdn.com/Shows/Going+Deep/C-and-Beyond-2012-Herb-Sutter-Concurrency-and-Parallelism Charles Charles 33 http://channel9.msdn.com/Shows/Going+Deep/C-and-Beyond-2012-Herb-Sutter-Concurrency-and-Parallelism/RSS C++ Concurrency Parallelism Programming Herb Sutter C++11 C++ and Beyond 2012 C++ and Beyond 2012: Panel - Convincing your Colleagues From C++ and Beyond 2012, Andrei, Herb and Scott present Convincing Your Colleagues - an interactive panel.

Abstract:

You can't do a better job if you don't change what you're doing, but change is hard.  It's especially hard when what needs to change is your colleagues' approach to software development. Moving your team forward often requires persuading your peers to change their behavior, sometimes to do something they're not doing, other times to stop doing something they've become accustomed to.  Whether the issue is to embrace or avoid C++ language features, to adopt new development tools or abandon old ones, to increase use of or scale back on overuse of design patterns, to adhere to coding standards, or any of the plethora of other matters that affect software creation, moving things forward typically requires getting your colleagues to buy into the change you're proposing.  But how can you do that?

In this panel session, Andrei, Herb, and Scott share how they go about convincing their colleagues to change and take questions from the audience. 

 

]]> http://channel9.msdn.com/posts/C-and-Beyond-2012-Panel-Convincing-your-Colleagues From C&#43;&#43; and Beyond 2012, Andrei, Herb and Scott present Convincing Your Colleagues - an interactive panel. Abstract: You can't do a better job if you don't change what you're doing, but change is hard.&nbsp; It's especially hard when what needs to change is your colleagues' approach to software development. Moving your team forward often requires persuading your peers to change their behavior, sometimes to do something they're not doing, other times to stop doing something they've become accustomed to.&nbsp; Whether the issue is to embrace or avoid C&#43;&#43; language features, to adopt new development tools or abandon old ones, to increase use of or scale back on overuse of design patterns, to adhere to coding standards, or any of the plethora of other matters that affect software creation, moving things forward typically requires getting your colleagues to buy into the change you're proposing.&nbsp; But how can you do that? In this panel session,&nbsp;Andrei, Herb, and Scott&nbsp;share how they go about convincing their colleagues to change and take questions from the audience.&nbsp; &nbsp; 2429 http://channel9.msdn.com/posts/C-and-Beyond-2012-Panel-Convincing-your-Colleagues Wed, 02 Jan 2013 15:36:37 GMT http://channel9.msdn.com/posts/C-and-Beyond-2012-Panel-Convincing-your-Colleagues Charles Charles 20 http://channel9.msdn.com/posts/C-and-Beyond-2012-Panel-Convincing-your-Colleagues/rss C++ Programming Herb Sutter C++11 Andrei Alexandrescu Scott Meyers C++ and Beyond 2012 C++ and Beyond 2012: Herb Sutter - You don't know [blank] and [blank] Herb Sutter presents a "startling realization he had about C++11", and he thinks it may be a bit startling for others too. Tune in.

This was filmed at C++ and Beyond 2012

Download Herb's slides for this session.

Abstract:

In addition to the many new C++11 features that everyone's listing, it has dawned on me over the winter that there's actually another major change that isn't being talked about anywhere, or even being listed as a change in C++11 at all as far as I know, because I and other key experts and committee members I've asked didn't fully realize that we altered the basic meaning of not one but two fundamental keywords in C++. It's a change that has profound consequences, that rewrites and/or invalidates several pieces of pre-C++11 design guidance, and that's directly related to writing solid code in a concurrent and parallel world. This isn't just an academic change, either — everyone is going to have to learn and apply the new C++11 guidance that we'll cover in this session.

I plan to talk about it first at C&B, in a session tentatively titled as above — I'll fill in the keywords later. You may already guess a few keyword candidates based on the description above, and here's a final hint: You'll hardly find two C++ keywords that are older, or whose meanings are more changed from C++98 to C++11. (No, they aren't auto and register.)

]]> http://channel9.msdn.com/posts/C-and-Beyond-2012-Herb-Sutter-You-dont-know-blank-and-blank Herb Sutter presents&nbsp;a &quot;startling realization he had about C&#43;&#43;11&quot;, and&nbsp;he thinks it may be a bit startling for others too. Tune in. This was filmed at C&#43;&#43; and Beyond 2012Download Herb's slides for this session. Abstract: In addition to the many new C&#43;&#43;11 features that everyone's listing, it has dawned on me over the winter that there's actually another major change that isn't being talked about anywhere, or even being listed as a change in C&#43;&#43;11 at all as far as I know, because I and other key experts and committee members I've asked didn't fully realize that we altered the basic meaning of not one but two fundamental keywords in C&#43;&#43;. It's a change that has profound consequences, that rewrites and/or invalidates several pieces of pre-C&#43;&#43;11 design guidance, and that's directly related to writing solid code in a concurrent and parallel world. This isn't just an academic change, either — everyone is going to have to learn and apply the new C&#43;&#43;11 guidance that we'll cover in this session. I plan to talk about it first at C&amp;B, in a session tentatively titled as above — I'll fill in the keywords later.&nbsp;You may already guess a few keyword candidates based on the description above, and here's a final hint: You'll hardly find two C&#43;&#43; keywords that are older, or whose meanings are more changed from C&#43;&#43;98 to C&#43;&#43;11. (No, they aren't&nbsp;auto and register.) 1847 http://channel9.msdn.com/posts/C-and-Beyond-2012-Herb-Sutter-You-dont-know-blank-and-blank Mon, 31 Dec 2012 14:45:00 GMT http://channel9.msdn.com/posts/C-and-Beyond-2012-Herb-Sutter-You-dont-know-blank-and-blank Charles Charles 28 http://channel9.msdn.com/posts/C-and-Beyond-2012-Herb-Sutter-You-dont-know-blank-and-blank/rss C++ Programming Programming Languages Herb Sutter C++11 C++ and Beyond 2012 C++ and Beyond 2012: Andrei Alexandrescu - Systematic Error Handling in C++ Andrei Alexandrescu presents "Systematic Error Handling in C++". This was filmed at C++ and Beyond 2012

Abstract:

Writing code that is resilient upon errors (API failures, exceptions, invalid memory access, and more) has always been a pain point in all languages. This being still largely an unsolved (and actually rather loosely-defined) problem, C++11 makes no claim of having solved it. However, C++11 is a more expressive language, and as always more expressive features can be put to good use toward devising better error-safe idioms and libraries.

This talk is a thorough visit through error resilience and how to achieve it in C++11. After a working definition, we go through a number of approaches and techniques, starting from the simplest and going all the way to file systems, storage with different performance and error profiles (think HDD vs. RAID vs. Flash vs. NAS), and more. As always, scaling up from in-process to inter-process to cross-machine to cross-datacenter entails different notions of correctness and resilience and different ways of achieving such.

To quote a classic, "one more thing"! An old acquaintance—ScopeGuard—will be present, with the note that ScopeGuard11 is much better (and much faster) than its former self.

Tune in. Learn. Thanks to Andrei, Herb and Scott for inviting C9 to film these wonderful sessions, rife with practical technical information for modern, professional C++ developers.

Get the slides.

]]> http://channel9.msdn.com/Shows/Going+Deep/C-and-Beyond-2012-Andrei-Alexandrescu-Systematic-Error-Handling-in-C Andrei Alexandrescu presents &quot;Systematic Error Handling in C&#43;&#43;&quot;. This was filmed at&nbsp;C&#43;&#43; and Beyond 2012 Abstract: Writing code that is resilient upon errors (API failures, exceptions, invalid memory access, and more) has always been a pain point in all languages. This being still largely an unsolved (and actually rather loosely-defined) problem, C&#43;&#43;11 makes no claim of having solved it. However, C&#43;&#43;11 is a more expressive language, and as always more expressive features can be put to good use toward devising better error-safe idioms and libraries. This talk is a thorough visit through error resilience and how to achieve it in C&#43;&#43;11. After a working definition, we go through a number of approaches and techniques, starting from the simplest and going all the way to file systems, storage with different performance and error profiles (think HDD vs. RAID vs. Flash vs. NAS), and more. As always, scaling up from in-process to inter-process to cross-machine to cross-datacenter entails different notions of correctness and resilience and different ways of achieving such. To quote a classic, &quot;one more thing&quot;! An old acquaintance—ScopeGuard—will be present, with the note that ScopeGuard11 is much better (and much faster) than its former self.Tune in. Learn. Thanks to Andrei, Herb and Scott for inviting C9 to film these wonderful sessions, rife with practical technical information for modern, professional C&#43;&#43; developers. Get the slides. 5198 http://channel9.msdn.com/Shows/Going+Deep/C-and-Beyond-2012-Andrei-Alexandrescu-Systematic-Error-Handling-in-C Mon, 10 Dec 2012 14:00:00 GMT http://channel9.msdn.com/Shows/Going+Deep/C-and-Beyond-2012-Andrei-Alexandrescu-Systematic-Error-Handling-in-C Charles Charles 33 http://channel9.msdn.com/Shows/Going+Deep/C-and-Beyond-2012-Andrei-Alexandrescu-Systematic-Error-Handling-in-C/RSS C++ Programming Programming Languages C++11 Andrei Alexandrescu C++ and Beyond 2012 C++ and Beyond 2012: Scott Meyers - Universal References in C++11 Scott Meyers presents "Universal References in C++11". This was filmed at C++ and Beyond 2012. This is the full session in all of its splendor. Huge thanks to Scott for allowing C9 to provide this excellent C++11 content to the world.

From Scott's recently published article in the October 2012 edition of ACCU's Overload:

Given that rvalue references are declared using "&&", it seems reasonable to assume that the presence of "&&" in a type declaration indicates an rvalue reference. That is not the case:

Widget&& var1 = someWidget; // here, "&&" means rvalue reference

auto&& var2 = var1; // here, "&&" does not mean rvalue reference

template<typename T>

void f(std::vector<T>&& param); // here, "&&" means rvalue reference

template<typename T>

void f(T&& param); // here, "&&" does not mean rvalue reference

In this article, I describe the two meanings of "&&" in type declarations, explain how to tell them apart, and introduce new terminology that makes it possible to unambiguously communicate which meaning of "&&" is intended. Distinguishing the different meanings is important, because if you think "rvalue reference" whenever you see "&&" in a type declaration, you'll misread a lot of C++11 code.

Tune in. Scott's an incredible presenter and it's well worth your time to both read his article and watch his presentation on the subject. Great stuff!

Download slides

]]> http://channel9.msdn.com/Shows/Going+Deep/Cpp-and-Beyond-2012-Scott-Meyers-Universal-References-in-Cpp11 Scott Meyers presents &quot;Universal References in C&#43;&#43;11&quot;. This was filmed at&nbsp;C&#43;&#43; and Beyond 2012. This is the full session in all of its splendor. Huge thanks to Scott for allowing C9 to provide this excellent C&#43;&#43;11 content to the world. From Scott's recently published article in the October 2012 edition of ACCU's Overload: Given that rvalue references are declared using &quot;&amp;&amp;&quot;, it seems reasonable to assume that the presence of &quot;&amp;&amp;&quot; in a type declaration indicates an rvalue reference. That is not the case: Widget&amp;&amp; var1 = someWidget; // here, &quot;&amp;&amp;&quot; means rvalue reference auto&amp;&amp; var2 = var1; // here, &quot;&amp;&amp;&quot; does not mean rvalue reference template&lt;typename T&gt; void f(std::vector&lt;T&gt;&amp;&amp; param); // here, &quot;&amp;&amp;&quot; means rvalue reference template&lt;typename T&gt; void f(T&amp;&amp; param); // here, &quot;&amp;&amp;&quot; does not mean rvalue reference In this article, I describe the two meanings of &quot;&amp;&amp;&quot; in type declarations, explain how to tell them apart, and introduce new terminology that makes it possible to unambiguously communicate which meaning of &quot;&amp;&amp;&quot; is intended. Distinguishing the different meanings is important, because if you think &quot;rvalue reference&quot; whenever you see &quot;&amp;&amp;&quot; in a type declaration, you'll misread a lot of C&#43;&#43;11 code. Tune in. Scott's an incredible presenter and it's well worth your time to both read his article and watch his presentation on the subject. Great stuff! Download slides 5023 http://channel9.msdn.com/Shows/Going+Deep/Cpp-and-Beyond-2012-Scott-Meyers-Universal-References-in-Cpp11 Tue, 09 Oct 2012 13:00:00 GMT http://channel9.msdn.com/Shows/Going+Deep/Cpp-and-Beyond-2012-Scott-Meyers-Universal-References-in-Cpp11 Charles Charles 46 http://channel9.msdn.com/Shows/Going+Deep/Cpp-and-Beyond-2012-Scott-Meyers-Universal-References-in-Cpp11/RSS C++ Programming Programming Languages Native Development C++11 Scott Meyers C++ and Beyond 2012 C++ and Beyond 2012: Alexandrescu, Meyers, and Sutter - Ask Us Anything Here is the Ask Us Anything panel from C++ and Beyond 2012.

Andrei Alexandrescu, Scott Meyers and Herb Sutter take questions from attendees. As expected, great questions and answers!

Tune in!

Table of contents (click the time codes ([xx:xx]) to hear the answers...):

Message passing primitives in future versions of the standard... [00:00]
Standardized unit testing framework... [02:55]
std::async... [04:30]
Standard modules proposal... [08:14]
Keyword additions and the standard library... [09:35]
Problems (and solutions) with exceptions... [12:50]
Future of concepts... [22:34]
std::thread and thread interruption... [23:03]
When to use the auto keyword (and when not to...)... [25:03]
More on auto (benefits of reduncancy, type conversion issues with bool to int?)... [29:31]
const and multithreaded programming, in C++11 const means thread safe, too... [35:00]
Yet more on auto (impact on rampant use and code readability/comprehension)... [42:42]
Compiler type deduction information (compiler switch that prints out auto deduced type information)... [50:18]
Printing out code for review that replaces auto with the actual type... [53:30]
auto and dynamic memory allocation... [54:59]
Useful, broadly-used concurrency libraries... [57:00]

]]> http://channel9.msdn.com/Shows/Going+Deep/C-and-Beyond-2012-Scott-Andrei-and-Herb-Ask-Us-Anything Here is the Ask Us Anything panel from C&#43;&#43; and Beyond 2012. Andrei Alexandrescu, Scott Meyers and Herb Sutter take questions from attendees. As expected, great questions and answers! Tune in! Table of contents (click the time codes ([xx:xx])&nbsp;to hear the answers...): Message passing primitives in future versions of the standard... [00:00]Standardized unit testing framework... [02:55]std::async... [04:30]Standard&nbsp;modules proposal... [08:14]Keyword additions and the standard library... [09:35]Problems (and solutions) with exceptions... [12:50]Future of concepts... [22:34]std::thread and thread interruption... [23:03]When to use the auto keyword (and when not to...)... [25:03]More on auto (benefits of reduncancy, type conversion issues with bool to int?)... [29:31]const and multithreaded programming, in C&#43;&#43;11 const means thread safe, too... [35:00]Yet more on auto (impact on rampant use and code readability/comprehension)... [42:42]Compiler type deduction information (compiler switch that prints out auto deduced type information)... [50:18]Printing out code for review that replaces auto with the actual type... [53:30]auto and dynamic memory allocation... [54:59]Useful, broadly-used concurrency libraries... [57:00] 3516 http://channel9.msdn.com/Shows/Going+Deep/C-and-Beyond-2012-Scott-Andrei-and-Herb-Ask-Us-Anything Tue, 18 Sep 2012 19:55:25 GMT http://channel9.msdn.com/Shows/Going+Deep/C-and-Beyond-2012-Scott-Andrei-and-Herb-Ask-Us-Anything Charles Charles 14 http://channel9.msdn.com/Shows/Going+Deep/C-and-Beyond-2012-Scott-Andrei-and-Herb-Ask-Us-Anything/RSS C++ Programming Languages Herb Sutter C++11 Andrei Alexandrescu Scott Meyers C++ and Beyond 2012 Alexandrescu, Meyers, Sutter: On Static If, C++11 in 2012, Modern Libraries, and Metaprogramming Channel 9 was invited to this year's C++ and Beyond to film some sessions (that will appear on C9 over the coming months!) and have a chat with the "Big Three": Andrei Alexandrescu, Scott Meyers, and Herb Sutter. If you are a C++ programmer, then you know these names very well. If you've not heard of C++ and Beyond, well, put it down as a must-attend event (let's hope they do it again in 2013!). You can see material from last year's event here.

At the end of day 2, Andrei, Herb and Scott graciously agreed to spend some time discussing various modern C++ topics and, even better, answering questions from the community. In fact, the questions from Niners (and a conversation on reddit/r/cpp) drove the conversation.

Huge thanks to Andrei, Herb, and Scott for their time and wisdom. Thanks, too, to the Niners who asked great questions!

Here's what happened:

[00:00] Themes for C++ in 2012 and beyond (and C++ and Beyond 2012)
[07:00] C++11 Efficiency and Concurrency/Parallelism (Standardization)
[12:12] dot_tom asks: When can we expect standardized modern libraries like, XML, File system, Web Services?
[15:00] ZippyV asks: Standardized modern libraries: What has the response been? Any unexpected requests?
[17:17] static if
[26:26] Matt_PD asks: Future of template metaprogramming? Standardizing static loops?
[40:07] More on template metaprogramming (and static if and enable_if)...
[50:05] async/await language feature in C++ would be nice, C&B 2013?

]]> http://channel9.msdn.com/Shows/Going+Deep/Alexandrescu-Meyers-Sutter-On-Static-If-C11-in-2012-Modern-Libraries-and-Metaprogramming Channel 9 was invited to this year's C&#43;&#43; and Beyond to film some sessions (that will appear on C9 over the coming months!) and have a chat with the &quot;Big Three&quot;: Andrei Alexandrescu, Scott Meyers, and Herb Sutter. If you are a C&#43;&#43; programmer, then you know these names very well. If you've not heard of C&#43;&#43; and Beyond, well, put it down as a must-attend event (let's hope they do it again in 2013!). You can see material from last year's event here.At the end of day 2, Andrei, Herb and Scott graciously agreed to spend some time discussing various modern C&#43;&#43; topics and, even better, answering questions from the community. In fact, the questions from Niners (and a conversation on reddit/r/cpp) drove the conversation. Huge thanks to Andrei, Herb, and Scott for their time and wisdom. Thanks, too,&nbsp;to the Niners who asked great questions!Here's what happened: [00:00] Themes for C&#43;&#43; in 2012 and beyond (and C&#43;&#43; and Beyond 2012)[07:00] C&#43;&#43;11 Efficiency and Concurrency/Parallelism (Standardization)[12:12] dot_tom asks: When can we expect standardized modern libraries like, XML, File system, Web Services?[15:00] ZippyV asks: Standardized modern&nbsp;libraries: What has the response been? Any unexpected requests?[17:17] static if[26:26] Matt_PD asks: Future of template metaprogramming? Standardizing static loops?[40:07] More on template metaprogramming (and static if and enable_if)...[50:05] async/await language feature in C&#43;&#43; would be nice, C&amp;B 2013? 3195 http://channel9.msdn.com/Shows/Going+Deep/Alexandrescu-Meyers-Sutter-On-Static-If-C11-in-2012-Modern-Libraries-and-Metaprogramming Tue, 21 Aug 2012 12:00:00 GMT http://channel9.msdn.com/Shows/Going+Deep/Alexandrescu-Meyers-Sutter-On-Static-If-C11-in-2012-Modern-Libraries-and-Metaprogramming Charles Charles 24 http://channel9.msdn.com/Shows/Going+Deep/Alexandrescu-Meyers-Sutter-On-Static-If-C11-in-2012-Modern-Libraries-and-Metaprogramming/RSS C++ Programming C++11 _techmeme C++ and Beyond 2012