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++

Locks are available in **three** different forms: 
1. `std::lock_guard` for simple use-cases
 
2. `std::unique-lock` for advanced use-cases 
3. `std::shared_lock` is available with C++14 and can be used to implement reader-writer locks. 

> <img src="/api/collection/10370001/6066104977850368/page/4580102618742784/image/6441996354846720" width="35"> Locks need the header `<mutex>`.

## RAII-Idiom (Resource Acquisition Is Initialization)
Locks take care of their resource following the _**RAII**_ idiom. A lock automatically binds its mutex in the constructor and releases it in the destructor. This reduces the risk of a deadlock because the runtime handles the mutex.

> If the lock goes out of scope, the resource will be immediately released.


Locks are available in **three** different forms: 
1. `std::lock_guard` for simple use-cases
 
2. `std::unique-lock` for advanced use-cases 
3. `std::shared_lock` is available with C++14 and can be used to implement reader-writer locks. 

> <img src="/api/collection/10370001/6066104977850368/page/4580102618742784/image/6441996354846720" width="35"> Locks need the header `<mutex>`.

# RAII-Idiom (Resource Acquisition Is Initialization)
Locks take care of their resource following the _**RAII**_ idiom. A lock automatically binds its mutex in the constructor and releases it in the destructor. This reduces the risk of a deadlock because the runtime handles the mutex.

> If the lock goes out of scope, the resource will be immediately released.


In this lesson, we will learn about different locks and their usage in embedded programming.

Introduction

Safety-Critical Systems

High Performance

Reduced Resources

Several Tasks Simultaneously

Conclusion

Locks

RAII-Idiom (Resource Acquisition Is Initialization)