Articles & Books

Upcoming C++ User Group meetings in September 2022

The monthly listing of upcoming C++ User Group meetings at Meeting C++:

Upcoming C++ User Group Meetings in September 2022

by Jens Weller

From the article:

The monthly listing of upcoming C++ User Group meetings! This time with a new group in Toulouse!

Meeting C++ online has a few meetings in September and hosts a lightning talk session tonight:

    31.8 C++ UG Meeting C++ online - C++ Lightning Talks
    1.9 C++ UG Meeting C++ online - C++ Community Planning session
    7.9 C++ UG Meeting C++ online - September - Corolib: distributed programming with C++ coroutines
    8.9 C++ UG Meeting C++ online - Meeting C++ online book & tool fair
    13.9 C++ UG Meeting C++ online - Hiring for C++ with Meeting C++
    20.9 C++ UG Meeting C++ online - Online C++ job fair (afternoon CEST)
    21.9 C++ UG Meeting C++ online - Online C++ job fair (evening CEST)

The concept of smart pointer static_ptr in C++

In this article we are discussing a new smart pointer type – static_ptr. It is most similar to std::unique_ptr without dynamic allocations.

The concept of smart pointer static_ptr<T> in C++

by Evgeny Shulgin

From the article:

We can create the move_assigner structure in a similar way. We could also make copy_constructer and copy_assigner, but our implementation doesn't require them. In static_ptr, the copy constructor and copy assignment operator will be deleted (as in unique_ptr).

About conditional breakpoints

A post on conditional breakpoints, including two surveys about their usage.

About conditional brealkpoits

by Jens Weller

From the article:

A few weeks ago someone asked me for advice on finding a specific bug in a larger C++ code base...

I don't remember much of the details, but one of the challenges was that at least some of the code based used public members, and in order to find the bug a change in these members is what they wanted to understand. Adding out put statements into a setter function wasn't possible, as the code did not have those. My suggestion was using a conditional breakpoint. And it also made me curious, if and how they're used with in our community.

Talks and Speaker for Meeting C++ 2022 released

Since yesterday its possible to have a first look at the program of Meeting C++ 2022

A first view on the talks and speakers of Meeting C++ 2022

by Jens Weller

From the article:

I'm excited to release this update for Meeting C++ 2022: the talks and speakers for this years conference!

As you can see in the talk listing, this is still an ongoing process, getting the speaker pictures from the new speakers for this year will still take a while. Creating the schedule will also take a few weeks, as of now Tracks A and B are planned on site, with Tracks C and D being part of the online part.

Improved automated instance construction in C++--Marius Elvert

The series continue.

Improved automated instance construction in C++

by Marius Elvert

From the article:

In my last blog post, I wrote about how I am automatically deducing constructor parameters in my dependency injection container. The approach had a major drawback: It worked only for 2 or more parameters, since there was an ambiguity with copy- or move-constructors with exactly one parameter...

Why do arrays have to be deleted via delete[] in C++

This note is for C++ beginner programmers who are wondering why everyone keeps telling them to use delete[] for arrays. But, instead of a clear explanation, senior developers just keep hiding behind the magical "undefined behavior" term. A tiny bit of code, a few pictures and a glimpse into nuts and bolts of the compilers – if interested, you're welcome to read.

Why do arrays have to be deleted via delete[] in C++

by Mikhail Gelvih

From the article:

This pointer in no case should be passed to the usual operator delete. Most likely, it will just remove the first element of the array and leave the others intact. Note that I wrote "most likely" for a reason, because no one can predict every possible outcome and the way the program will behave. It all depends on what objects were in the array and whether their destructors did something important. As a result, we get the traditional undefined behavior. This is not what you would expect when trying to delete an array.