Presenter Interviews: Emery Berger

by Bob Steagall

In this week’s presenter interview, Kevin talks with Professor Emery Berger about his time working with memory management in C++, what he is looking forward to at this years conference, and his session Mesh: Automatically Compacting Your C++ Application’s Memory.

Call for Open Content Sessions

As we do every year, we offer Open Content session in the early morning, over lunch, and in the evening...

Can I has grammar?

by Timur Doumler

Lightning talk.

105 STL Algorithms in Less Than an Hour

by Jonathan Boccara

We are all aware that we should know the STL algorithms. Including them in our designs allows us to make our code more expressive and more robust. And sometimes, in a spectacular way.

But do you know your STL algorithms?

In this presentation, you’ll see the 105 algorithms that the STL currently has, including those added in C++11 and C++17. But more than just a listing, the point of this presentation is to highlight the different groups of algorithms, the patterns they form in the STL, and how the algorithms relate together. And all this in an entertaining way.

This kind of big picture is the best way I know to actually remember them all, and constitute a toolbox chock-full of ways to make our code more expressive and more robust.

Presenter Interviews: Matthew Butler

by Bob Steagall

In this week’s presenter interview, Kevin chats with Matthew Butler today about his upcoming class at CppCon, Exploiting Modern C++: Building Highly-Dependable Software, his first WG21 meeting in Cologne, and his upcoming CppCon talk If You Can’t Open It, You Don’t Own It.

C++ Core Guidelines: More Non-Rules and Myths

by Rainer Grimm

Demystifying non-rules and myths in C++ is a laborious but absolutely necessary job. The goal is simple: use the powerful tool C++ appropriately...

Thoughts on a more powerful and simpler C++ (5 of N)

by Herb Sutter

Perhaps the most important thing we can do for C++ at this point in its evolution is to make sure we preserve its core strengths while also directing its evolution in ways that make it simpler to use. That is my own opinion at least, so this talk starts with a perspective question: What “is C++,” really? The language continues to evolve and change; as it does so, how can we be sure we’re picking C++ evolutionary improvements that not only don’t lose its “C++-ic” qualities, but make it a better C++ than ever?

At recent CppCons, I’ve spoken about several of my own personal C++ evolution efforts and experiments, and why I think they’re potentially important directions to explore for making C++ both more powerful and also simpler to use. The bulk of the talk is updates on two of these:

1. Lifetime and dangling: At CppCon 2015, Bjarne Stroustrup and I launched The C++ Core Guidelines in our plenary talks. In my part starting at 29:06, I gave an early look at my work on the Guidelines “Lifetime” profile, an approach for diagnosing many common cases of pointer/iterator dangling at compile time, with demos in an early MSVC-based prototype. For this year’s CppCon, I’ll cover what’s new, including:
    • use-after-move diagnoses
    • better support for the standard library out of the box without annotation
    • more complete implementations in two compilers: in MSVC as a static analysis extension, and in a Clang-based implementation that is efficient enough to run during normal compilation
    • the complete 1.0 Lifetime specification being released on the Guidelines’ GitHub repo this month

I’ll summarize the highlights but focus on what’s new, so I recommend rewatching that talk video as a refresher for background for this year’s session.

2. Metaclasses: In my CppCon 2017 talk, I gave an early look at my “metaclasses” proposal to use compile-time reflection and compile-time generation to make authoring classes both more powerful and also simpler. In this case, “simpler” means not only eliminating a lot of tedious boilerplate, but also eliminating many common sources of errors and bugs. For this year, we’ll cover what’s new, including:
    • an update on the Clang-based implementation, which now supports more use cases including function parameter lists
    • new examples, including from domains like concurrency
    • an updated P0707 paper, with more links to working examples live on Godbolt, being posted in the next few weeks for the pre-San Diego committee mailing

CppCon Advice

Hello all, I've been programming in C++ for about 5 years now, 4 years in a university setting and 1 at my current employer. Recently, I put in a request to attend CppCon and it was accepted, which I'm thrilled about...

CppCon 2019 Class, Presentation and Book Signing

by Anthony Williams

It is now less than a month to this year's CppCon, which is going to be in Aurora, Colorado, USA for the first time this year, in a change from Bellevue where it has been for the last few years...

How to set up PVS-Studio in Travis CI using the example of PSP game console emulator

by Maxim Zvyagintsev

At the beginning of the travis_install function we install the compilers we need using environment variables. Then, if the $PVS_ANALYZE variable stores the value of Yes (we specified it in the env section when configuring the build matrix), we install the pvs-studio package. Besides it, there are also libio-socket-ssl-perl and libnet-ssleay-perl packages, but they are needed to send the results by mail, so they are not necessary if you have chosen another way of report delivery.