Call for Papers

by the ACCU

The ACCU 2023 conference will be from 2023-04-19 to 2023-04-22, with pre-conference workshops on 2023-04-17 and 2023-04-18.

The ACCU 2023 will be a hybrit event.

Historically, ACCU has a lot of C++ and C content, and is proud of that: ACCU is the foremost annual conference for people interested in C++ and C, at least in and around the UK. But it is not just a C++ and C conference, ACCU is about programming in whatever language people are using, with whatever tools and processes people are using: D, Chapel, Java, Kotlin, C#, F#, Groovy, Rust, Go, Python, Ruby, Lisp, to name just a few programming languages about which there have been sessions at ACCU conferences. Git, Mercurial, CMake, Meson, TDD, BDD, all these tools and techniques have been the focus of sessions at ACCU. The ACCU Conference is looking for sessions that will be interesting to people who create software.
The ACCU Conference is put on by ACCU (https://accu.org), but is open to anyone who wishes to be there either as a presenter or an attender.

The Call for Papers lasts for about 3 weeks and will close on Monday 7th November 2022 at 23:59:59 GMT.

The Bridge Pattern

by Rainer Grimm

In C++, a simplified version of the Bridge Pattern is often used. ... The key idea of the Pimpl Idiom is that the implementation of the class is hidden behind a pointer. Here is a recipe for implementing the Pimpl Idiom: ...

CppCon 2022 Keynote on C++ Math: Lisa Lippincott

Lisa Lippincott on C++ math... her CppCon 2022 Online Opening Keynote in Aurora, Colorado!

CppCon 2022 keynote: How C++23 changes the way we write code

Timur Doumler

Timur Doumler on C++23 at his CppCon 2022 keynote in Aurora, Colorado!

This video is in “prerelease” and cannot be found directly on our YouTube channel, instead we are providing a direct link here only! Feel free to share this with colleagues and friends and impress them with your insider access...

The power of ref-qualifiers

by Andreas Fertig

... What I have illustrated is that there is an issue with range-based for-loops. In (1), we call GetKeeper().items() in the head of the range-based for-loop. By doing this, we create a dangling reference.

ref-qualifiers to the rescue

Now, this brings us to ref-qualifiers. They are often associated with move semantics, but we can use them without move. However, we will soon see why ref-qualifiers make the most sense with move semantics.

A version of Keeper with ref-qualifiers looks like Listing 2...

The gotcha of the C++ temporaries that don’t destruct as eagerly as you thought

by Raymond Chen

Forgetting to take a lock when updating variables is a common mistake. One way to make the mistake harder to make is to force the access to occur through some mechanism that proves that you possess the lock. Maybe something like this: ...

Highlighting the student and support tickets for Meeting C++ 2022

by Jens Weller

With the schedule published, I'd like to highlight the student and support tickets for Meeting C++ 2022.

For a few years now Meeting C++ has hosted programs to give students, underrepresented folks and those who can't afford a ticket access to the conference. This is supported through the ticket sales and some times sponsorships.

Deferred argument evaluation

by Joaquín M López Muñoz

Ideally, we'd like for try_emplace to not create the object except when really needed. What we're effectively asking for is some sort of technique for deferred argument evaluation. As it happens, it is very easy to devise our own: ...

The Singleton: The Alternatives Monostate Pattern and Dependency Injection

by Rainer Grimm

So far, I have discussed in my previous posts the Singleton Pattern, and its pros and cons. One question is still open: What alternatives for the Singleton Pattern are available? Today, I write about the Monostate Pattern and Dependency Injection...

C++20 Concurrency: Barrier

by Gajendra Gulgulia

In this article, I’ll present a simple example of std::barrier by means of game players playing a hypothetical card game and go into the details of the api of std::barrier in another article...