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
A [std::unique_ptr](http://en.cppreference.com/w/cpp/memory/unique_ptr) automatically and exclusively manages the lifetime of its resource according to the RAII idiom. `std::unique_ptr` should be your first choice since it functions without memory or performance overhead.

[std::unique_ptr](http://en.cppreference.com/w/cpp/memory/unique_ptr) exclusively takes care of its resource. It automatically releases the resource if it goes out of scope. No copy semantic is required, and it can be used in containers and algorithms of the Standard Template Library. `std::unique_ptr` is as cheap and fast as a raw pointer when no special delete is used. 


## Characteristics
Before you go into the usage of `std::unique_ptr`, we will present you its characteristics in a few bullet points.

The `std::unique_ptr`:

* can be instantiated with and without a resource.
* manages the life cycle of a single object but although of an array of objects.
* transparently offers the interface of the underlying resource.
* can be parametrized with its own deleter function.
* can be moved (move semantic).
* can be created with the helper function `std::make_unique`.

### Replacement for std::auto_ptr
><span style="font-size:2em" >⚠️</span> **Don't use std::auto_ptr**
\
Classical C++98 has a smart pointer `std::auto_ptr`, which exclusively addresses the lifetime of a resource. `std::auto_ptr` has a conceptional issue. If you implicitly or explicitly copy an `std::auto_ptr`, the resource is moved. Therefore, rather than utilizing copy semantic, you have a hidden move semantic, leading to undefined behavior. So `std::auto_ptr` is deprecated in C++11 and removed in C++17. Instead, you should use `std::unique_ptr`. You can neither implicitly or explicitly copy a `std::unique_ptr`; you can only move it.



# Introduction
A [std::unique_ptr](http://en.cppreference.com/w/cpp/memory/unique_ptr) automatically and exclusively manages the lifetime of its resource according to the RAII idiom. `std::unique_ptr` should be your first choice since it functions without memory or performance overhead.

[std::unique_ptr](http://en.cppreference.com/w/cpp/memory/unique_ptr) exclusively takes care of its resource. It automatically releases the resource if it goes out of scope. No copy semantic is required, and it can be used in containers and algorithms of the Standard Template Library. `std::unique_ptr` is as cheap and fast as a raw pointer when no special delete is used. 


## Characteristics
Before you go into the usage of `std::unique_ptr`, we will present you its characteristics in a few bullet points.

The `std::unique_ptr`:

* can be instantiated with and without a resource.
* manages the life cycle of a single object but although of an array of objects.
* transparently offers the interface of the underlying resource.
* can be parametrized with its own deleter function.
* can be moved (move semantic).
* can be created with the helper function `std::make_unique`.

### Replacement for std::auto_ptr
><span >⚠️</span> **Don't use std::auto_ptr**
\
Classical C++98 has a smart pointer `std::auto_ptr`, which exclusively addresses the lifetime of a resource. `std::auto_ptr` has a conceptional issue. If you implicitly or explicitly copy an `std::auto_ptr`, the resource is moved. Therefore, rather than utilizing copy semantic, you have a hidden move semantic, leading to undefined behavior. So `std::auto_ptr` is deprecated in C++11 and removed in C++17. Instead, you should use `std::unique_ptr`. You can neither implicitly or explicitly copy a `std::unique_ptr`; you can only move it.



In this lesson, we will examine the first type of smart pointer – the unique pointer. It limits access to its resource, thereby maintaining its privacy.

Introduction

Safety-Critical Systems

High Performance

Reduced Resources

Several Tasks Simultaneously

Conclusion

Smart Pointers: Unique Pointers

Introduction