Gain insights into using Modern C++ for embedded programming. Learn about safety-critical systems, optimize performance, manage limited resources, and handle parallel execution effectively.

waleed1.tar.gz

C++11

C++ 17

Embedded Programming with Modern C++  is highly valuable for each professional programmer.

In the past, embedded and system programming have had their pitfalls, but modern C++ has been designed to be a better language for this type of development, addressing the previous pitfalls/requirements explicitly. What are these requirements? Embedded systems deal with safety-critical systems, meaning they must guarantee high performance combined with limited resources, while also working in parallel.

The scope of this course goes beyond just embedded programming. Developers who write servers, games, or trading systems may especially benefit from this course because they also have to deal with safety-critical systems, high performance, reduced resources, and parallel execution in their jobs.

To get the most out of the course, you only need a basic understanding of C++. Building off this understanding, this course goes over all the essentials of embedded programming with Modern C++.

Let's get started!

Embedded Programming with Modern C++

## Introduction
[std::shared_ptr](http://en.cppreference.com/w/cpp/memory/shared_ptr) shares the ownership of the resource. They have two handles: one for the resource and one for the reference counter. By copying a `std::shared_ptr`, the reference count is increased by one. It is decreased by one if the `std::shared_ptr` goes out of scope. If the reference counter becomes the value 0, the C++ runtime automatically releases the resource, since there is no `std::shared_ptr` referencing the resource. The release of the resource occurs exactly when the last `std::shared_ptr` goes out of scope. The C++ runtime guarantees that the call of the reference counter is an atomic operation. Due to this management, `std::shared_ptr` consumes more time and memory than a raw pointer or `std::unique_ptr`.


Take a look at the image below to better visualize the concept. 






# Introduction
[std::shared_ptr](http://en.cppreference.com/w/cpp/memory/shared_ptr) shares the ownership of the resource. They have two handles: one for the resource and one for the reference counter. By copying a `std::shared_ptr`, the reference count is increased by one. It is decreased by one if the `std::shared_ptr` goes out of scope. If the reference counter becomes the value 0, the C++ runtime automatically releases the resource, since there is no `std::shared_ptr` referencing the resource. The release of the resource occurs exactly when the last `std::shared_ptr` goes out of scope. The C++ runtime guarantees that the call of the reference counter is an atomic operation. Due to this management, `std::shared_ptr` consumes more time and memory than a raw pointer or `std::unique_ptr`.


Take a look at the image below to better visualize the concept. 






Next, we will go over shared pointers, which follow the principle of keeping a reference count to maintaining the count of its copies. The lesson below elaborates further.

Introduction

Safety-Critical Systems

High Performance

Reduced Resources

Several Tasks Simultaneously

Conclusion

Smart Pointers: Shared Pointers

Introduction