Preconditions, Postconditions, Invariants - How They Help Write Robust Programs

By Andrzej Krzemienski | Feb 18, 2021 12:43 PM | Tags: None

An introduction to preconditions, postconditions and invariants.

Preconditions, Postconditions, Invariants –- How They Help Write Robust Programs

by Andrzej Krzemieński

From the video description:

Preconditions, postconditions, and invariants are part of what is often called Design by Contract, or Contract Programming. Even if you haven't heard of them, you are probably using them already. In this talk, we are going to see what they are, and how people and tools can make use of them.

unique_ptr, shared_ptr, weak_ptr, or reference_wrapper for class relationships -- Hitesh Kumar

By Hitesh Kumar | Feb 18, 2021 12:35 PM | Tags: None

Expressing class relationships with unique_ptr, shared_ptr, weak_ptr, and reference_wrapper.

unique_ptr, shared_ptr, weak_ptr, or reference_wrapper for class relationships

by Hitesh Kumar

From the article:

Classes communicate with each other by having handles as members that refer to other classes. The choice of those referring-handles (e.g., pointers or references) is mostly driven by ownership or control-over-lifetime semantics.

Why PVS-Studio Uses Data Flow Analysis: Based on Gripping Error in Open Asset Import Library

By Andrey Karpov | Feb 18, 2021 10:20 AM | Tags: value range analysis static code analysis pvs-studio data flow analysis cwe-571 bugs

An essential part of any modern static code analyzer is data flow analysis. However, from an outside perspective, the use of data flow analysis and its benefit is unclear.

Why PVS-Studio Uses Data Flow Analysis: Based on Gripping Error in Open Asset Import Library

by Andrey Karpov

From the article:

It all started with checking the latest version of the Qt 6 library. There was a separate usual article on this, where I'd described 77 errors found. It turned out that at first, I decided to flip through the report, not excluding the third-party libraries' warnings. In other words, I didn't exclude the warnings related to \src\3rdparty in the settings. It so happened that I immediately ran up against a gripping error example in the Open Asset Import Library. So, I decided to write this extra little note about it.

Modern C++: Safety and Expressiveness with override and final

By Adrien Hamelin | Feb 18, 2021 08:25 AM | Tags: c++11

Back to basics.

Modern C++: Safety and Expressiveness with override and final

by Bartlomiej Filipek

From the article:

While C++11 is with us for a decade now, it’s good to go back and recall some of its best features. Today I’d like to consider override and final keywords which add a crucial safety when you build class hierarchies with lots of virtual member functions.

See how to prevent common bugs, and how to leverage tools to make your code safer...

An Improved Thread with C++20--Rainer Grimm

By Adrien Hamelin | Feb 18, 2021 08:21 AM | Tags: c++20

More about c++20.

An Improved Thread with C++20

by Rainer Grimm

From the article:

std::jthread stands for joining thread. In addition to std::thread (C++11), std::jthread automatically joins in its destructor and can cooperatively be interrupted. Read in this post to know why std::jthread should be your first choice...

Colony – A brief history of timing--Matt Bentley

By Adrien Hamelin | Feb 18, 2021 08:18 AM | Tags: None

A different container.

Colony – A brief history of timing

by Matt Bentley

From the article:

Back in 2014 I began designing a game engine. Experienced programmers and curmudgeonly lecturers will tell you that if you make a game engine, you’ll never make a game – which is true, but sort of irrelevant. You will learn so much from making a game engine, you probably won’t care about the game by the end of it. The main reason I wanted to develop a game engine was that I was tired of seeing very basic 2D games with incredibly bad performance even on fast computers. If we got 15 frames-per-second on Intel 386 processors in the 1990s, why was it so hard for modern 2D games to achieve the same speed on exponentially-better hardware?

Colony – A brief history of timing

By Adrien Hamelin | Feb 18, 2021 07:51 AM | Tags: None

HPX V1.6.0 released -- STE||AR Group

By Hartmut Kaiser | Feb 18, 2021 07:18 AM | Tags: performance parallelism heterogeneous computing distributed computing concurrency c++20 c++17 c++14 c++11

The STE||AR Group has released V1.6.0 of HPX -- A C++ Standard library for parallelism and concurrency.

HPX V1.6.0 Released

The newest version of HPX (V1.6.0) is now available for download! This release continues the focus on C++20 conformance with multiple new algorithms adapted to be C++20 conformant and becoming customization point objects (CPOs). We have added experimental support for HIP, allowing existing CUDA features to now be compiled with hipcc and run on AMD GPUs as well. We have also continued improving the performance of the parallel executors, and added an experimental fork-join executor. The full list of improvements, fixes, and breaking changes can be found in the release notes.

    HPX is a general purpose parallel C++ runtime system for applications of any scale. It implements all of the related facilities as defined by the C++ Standard. As of this writing, HPX provides the only widely available open-source implementation of the new C++17 parallel algorithms. Additionally, HPX implements functionalities proposed as part of the ongoing C++ standardization process, such as large parts of the features related parallelism and concurrency as specified by the upcoming C++20 Standard, the C++ Concurrency TS, Parallelism TS V2, data-parallel algorithms, executors, and many more. It also extends the existing C++ Standard APIs to the distributed case (e.g. compute clusters) and for heterogeneous systems (e.g. GPUs).

    HPX seamlessly enables a new Asynchronous C++ Standard Programming Model that tends to improve the parallel efficiency of our applications and helps reducing complexities usually associated with parallelism and concurrency.

Looking for C++ Employers for the online C++ Job fair on March 16th

By Meeting C++ | Feb 16, 2021 05:42 AM | Tags: meetingcpp jobs community

Meeting C++ organizes the 2nd online C++ job fair on March 16th!

Looking for C++ Employers for March 16th

by Jens Weller

From the article:

Meeting C++ organizes the 2nd online C++ Job fair on March 16th!

The first online job fair in October 2020 was a big success, and now with the world coming back from the pandemic, I'd like to continue organizing these events online. This time the event will take place in wonder.me, a platform where users can freely roam around on a virtual map and engage in conversations by joining a circle. Join the Meeting C++ online User Group for further updates on the event.

The virtual job fair where you can attend and talk to different employers or job searchers is planned for March 16th. For Tuesday afternoon from 15-18:00 (CET) you'll be able to join the event and talk to employers and other job searchers. Each employer that registers will have its own named area. Employers need to sign up until March 10th.

Overload 161 is now available

By Adrien Hamelin | Feb 10, 2021 02:13 PM | Tags: community

ACCU’s Overload journal of February 2021 is out. It contains the following C++ related articles.

Overload 161 is now available

From the journal:

In. Sub. Ordinate.
By Frances Buontempo
Mindless rebellion is mindless. Frances Buontempo encourages mindful consideration of when to refuse.

A Case Against Blind Use of C++ Parallel Algorithms
By Lucian Radu Teodorescu
C++17 introduced parallel algorithms. Lucian Radu Teodorescu reminds us we need to think when we use them.

C++ – an Invisible Foundation of Everything
By Bjarne Stroustrup
What is C++ and why do people still use it? Bjarne Stroustrup provides a short note answering these questions.

Test Precisely and Concretely
By Kevlin Henney
Tests can hit complete coverage but fail to communicate. Kevlin Henney reminds us that assertions should be necessary, sufficient, and comprehensible.

Afterwood
By Chris Oldwood
Think you’ve learnt it all? Chris Oldwood reminds us that unlearning then becomes our next problem.