C++ and Beyond

Channel 9 has posted another video  - Herb Sutter’s “You don’t know [blank] and [blank]” presented at C++ and Beyond 2012 last summer in Asheville, NC. Here’s the link: You don’t know [blank] and [blank].

Here is the 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.)

Enjoy!

Microsoft’s Channel 9 recently posted a video from C++ and Beyond 2012: Panel - Convincing your Colleagues.

Here is the 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.

Channel 9 has posted a video of Herb Sutter’s “C++ Concurrency” presented at C++ and Beyond 2012 last summer in Asheville, NC. Here’s the link: C++ Concurrency.

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.

Enjoy!

There will be a C++ and Beyond 2013!  The dates are tentatively set to be December 8-11, so block that time out on your calendar.  We have a venue picked out, but we haven’t signed a contract yet, so I can’t make any announcement about where C&B 2013 will take place.  I expect to be able to tell you all about it within the next few weeks, however.

Until then, hold December 8-11, 2013, for more in-depth, in-sightful, in-triguing, in-vestigations into the world of C++…and Beyond :-)

Scott