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
Tasks were one of the latest additions to the C++11 standard, and they offer a better abstraction than threads.

In addition to threads, C++ has tasks to perform work asynchronously. Tasks need the `<future>` header. A task will be parameterized with a work package, and it consists of the two associated components: a `promise` and a `future`. Both are connected via data channel. 

The `promise` executes the work packages and puts the result in the data channel. The associated `future` picks up the result. Both communication endpoints can run in separate threads. What is special is that the `future` can pick up the result at a later time, meaning that the resulting calculation by the `promise` is independent of the query of the result by the associated `future`.
.

>🔑 **Regard tasks as data channels between communication endpoints**
> 
>Tasks behave like data channels between communication endpoints. One endpoint of the data channel is called the `promise`. The other endpoint of the data channel is called the `future`. These endpoints can exist in the same or in different threads. The `promise` puts its result in the data channel. The `future` waits for it and picks it up.

# Introduction
Tasks were one of the latest additions to the C++11 standard, and they offer a better abstraction than threads.

In addition to threads, C++ has tasks to perform work asynchronously. Tasks need the `<future>` header. A task will be parameterized with a work package, and it consists of the two associated components: a `promise` and a `future`. Both are connected via data channel. 

The `promise` executes the work packages and puts the result in the data channel. The associated `future` picks up the result. Both communication endpoints can run in separate threads. What is special is that the `future` can pick up the result at a later time, meaning that the resulting calculation by the `promise` is independent of the query of the result by the associated `future`.
.

>🔑 **Regard tasks as data channels between communication endpoints**
> 
>Tasks behave like data channels between communication endpoints. One endpoint of the data channel is called the `promise`. The other endpoint of the data channel is called the `future`. These endpoints can exist in the same or in different threads. The `promise` puts its result in the data channel. The `future` waits for it and picks it up.

# Introduction
Tasks were one of the latest additions to the C++11 standard, and they offer a better abstraction than threads.

In addition to threads, C++ has tasks to perform work asynchronously. Tasks need the `<future>` header. A task will be parameterized with a work package, and it consists of the two associated components: a `promise` and a `future`. Both are connected via data channel. 

The `promise` executes the work packages and puts the result in the data channel. The associated `future` picks up the result. Both communication endpoints can run in separate threads. What is special is that the `future` can pick up the result at a later time, meaning that the resulting calculation by the `promise` is independent of the query of the result by the associated `future`.
.

>🔑 **Regard tasks as data channels between communication endpoints**
> 
>Tasks behave like data channels between communication endpoints. One endpoint of the data channel is called the `promise`. The other endpoint of the data channel is called the `future`. These endpoints can exist in the same or in different threads. The `promise` puts its result in the data channel. The `future` waits for it and picks it up.

In this lesson, we will see how  tasks should be your first choice in the general case of multithreading.

Introduction

Safety-Critical Systems

High Performance

Reduced Resources

Several Tasks Simultaneously

Conclusion

Tasks

Introduction