Home > Articles > Programming > C/C++

Design and Evolution of C++: Video Podcast Transcript

In this transcription of an OnSoftware session, Bjarne Stroustrup and Herb Sutter talk with Ted Neward about writing good books, the (lack of) hype for C++, and how different programming will be in a multicore world.
Like this article? We recommend

Welcome to OnSoftware—conversations with thought leaders in software development. In this session, the creator of C++ (Bjarne Stroustrup) and author Herb Sutter discuss the program's creation and evolution over the years.

Ted Neward: Gentleman, good morning. For the benefit of our audience members who may not recognize you by sight, why don't you give us a quick intro of who each of you are and what you've been doing the last couple of years?

Herb Sutter: Okay, well, how about we do it for each other? I didn't tell him this [points to Stroustrup], but this is Bjarne Stroustrup. He is a professor at Texas A&M University, inventor of C++, AT&T Fellow, and National Academy of Engineering winner—congratulations again from last year.

Bjarne Stroustroup: Thanks. [Points to Sutter.] And this is Herb Sutter. He has worked for Microsoft for a few years. He is the convener—that's sort of the chairman—of the ISO C++ committee, and a long-term C++ user helping with the standard.

Ted: Cool, excellent—and I didn't tell you this, Mr. Stroustrup, but I have actually been a long-time fan of both of your books, having been a C++ programmer prior to my current engagements. One of the books that I actually found particularly interesting (both in my C++ days as well as today) was The Design and Evolution of C++. I'm sort of curious: There has been a lot of discussion around the design of programming languages—and now we've started talking about domain-specific languages and so forth. Sort of curious, as one who has been through the trenches, so to speak, of programming language design: What did you find in C++'s history that you think is broadly applicable to a lot of different languages? And obviously [gestures to Sutter], you've been involved with C++ for a while, too. What you guys see as particularly relevant even today that the world can learn from your experience?

Bjarne: The first observation I'll make is, it's interesting that we're here and it's an Addison-Wesley crowd—and we both [points to Sutter and himself] forgot to mention that we were authors! The Design and Evolution you referred to is a book that was most fun for me to write.

Ted: It looks like it.

Bjarne: It's very rare that you can find something where you can say thanks to your friends, and explain where you put your foot in your mouth, and things like that. The academic book formats generally don't allow that. But anyway, I think that what's interesting about C++ and that you can take away from [the book] is that there really is a place in the world for a language that can do close-to-the-hardware work—can deal very effectively with the resources and yet has the abstraction mechanisms that you can use for really demanding larger applications, and that's the C++ model. People tend to forget it in idle hype or the duration—that it actually works for that.

Ted: There's some hype surrounding these languages? You shock me, you surprise me. You stun me!

[Neward and Sutter laugh.]

Bjarne: We don't have any hype machine—we've never had it.

Herb: It's a real problem!

Bjarne: Yeah, it's a real problem, because you hear everything good about other languages. They have people that are paid to distribute the good news, even make the good news; whereas, if something good happens in the C++ community, nobody hears about it—because, well, we don't have any marketing budget.

Ted: Right, right. I will admit that just recently I was rummaging around, if you will, across the C++ parts of the Web and discovered the boost libraries and was quite pleasantly surprised. As a matter of fact, I blogged at one point, what have they done to my language? Where was this, like, years ago? I might never have moved off of it.

Herb: Well, we have an answer for you, by the way.

Ted: Okay, what have you done?

Herb: Not all, but many of the boost libraries are in the next standard of C++, the one we're about finishing. So when you hear us talk about C++0x, that's just a placeholder for the next revision of C++, which we're working on. And currently the goal is that "x is not hex"—that we're going to be done next year, in 2008, and so we'll fill that into "C++ '08" or "'09." But much of boost is already in there, hash-based containers and smart pointers, and various other things that you would expect, right down to numerics work and being able to take advantage of some of the libraries that normally people have had to go to vendors for, now can be in the standard—things that everybody can and should be able to use.

Ted: Okay, see, I still remember the C++ in the days when everybody had to write their own string class, so I'm quite glad to hear some of this.

Herb: Oh, you've been around for a long time.

Bjarne: That's a long time ago. The other thing we should probably mention in connection with C++0x is the threads library that will be one of the major [features].

Ted: So we're getting concurrency support.

Bjarne: Oh, yes, definitely.

Herb: That's something that's just non-negotiable. Any language from this point forward that ignores concurrency is basically not relevant for mainstream applications.

Ted: There's this article by this guy not too long ago, something about "There's no more free lunch." Would you know anything about that? [Smiles at Sutter, who wrote the aforementioned article.]

Herb: Oh yeah, I heard about that article. I saw it on Slashdot or something. [Laughs.]

Ted: You want to speak to that for a second?

Herb: Yeah, well, the "free lunch is over" article that I wrote was actually interesting because I had an article deadline and had to write [something], and I thought, well, this has been on my mind, so I wrote it—and it just took on a life of its own. I touched a nerve, and it was something that really was relevant because we're standing at a crossroads. For the first time in 50 years, which is the whole history of computing, mainstream hardware is no longer a von Neumann machine—a single-processor unit, which conceptually is just talking [about] the memory or tape or something.

Ted: Right.

Herb: And that means that we have a whole new architecture. Everything is changing underneath us. And a lot of people, I think, are still ignoring the impact of that. They sort of know intellectually, "Oh, yeah, we're getting more cores." They don't really understand what it means. They may even understand, "I have to write my software differently," with some vague notion of differently—and we're going to spend a number of years of conferences and in tooling, educating people and enabling them with tools on how to do that.

But the key thing to keep in mind is this: Just because you've got lots of, for example, x86 cores, and the instruction set is the same—it ain't the same hardware, it is not the same architecture. People are fooled, because they say, "Oh, it's still x86." But it is very different. It is like a whole new kind of machine. And so, on the one hand, that means that there's going to be a lot of new stuff to learn and a lot of techniques that we're going to change. But it's also a really great opportunity because, for the first time in 50 years, it's "green field." Everybody is looking forward to some exciting times of being able to do stuff we have never been able to do before because of lack of compute power.

Ted: Well, and just think of all the new books we can write.

Herb: Well, there you go. Yeah, that's something of interest to you, I see?

[Neward laughs.]

Herb: So what kind of concurrency book can we look forward to, or something different—?

Ted: Oh, from me? Oh, no, no—that's for you guys to work out.

Bjarne: Actually, I find it scary. Writing a decent book takes forever. So the burden of having to write those books is quite a lot. But it'll be nice to get back to concurrency work. That was where I started, distributed systems and concurrency. I think it's worth mentioning that there are lots of things in C++ that [are] not in the standards. One of the things the language is for is building libraries. So, much of the concurrency people get today in their systems is written in C++, it's just not [in the] standard. It's a library that people [are] using. So their threads libraries is probably a C++ library, whether it is on Microsoft or on Linux or something like that. So there's more to C++ than you can read in the standards document.

For more information, visit onpodcastweekly.com and subscribe to all our podcasts. Brought to you by the publishing imprints and information portal of Pearson Education.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020