Book Image

C++ Reactive Programming

By : Praseed Pai, Peter Abraham
Book Image

C++ Reactive Programming

By: Praseed Pai, Peter Abraham

Overview of this book

Reactive programming is an effective way to build highly responsive applications with an easy-to-maintain code base. This book covers the essential functional reactive concepts that will help you build highly concurrent, event-driven, and asynchronous applications in a simpler and less error-prone way. C++ Reactive Programming begins with a discussion on how event processing was undertaken by different programming systems earlier. After a brisk introduction to modern C++ (C++17), you’ll be taken through language-level concurrency and the lock-free programming model to set the stage for our foray into the Functional Programming model. Following this, you’ll be introduced to RxCpp and its programming model. You’ll be able to gain deep insights into the RxCpp library, which facilitates reactive programming. You’ll learn how to deal with reactive programming using Qt/C++ (for the desktop) and C++ microservices for the Web. By the end of the book, you will be well versed with advanced reactive programming concepts in modern C++ (C++17).
Table of Contents (20 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

Managing threads


At runtime, the execution starts at the user entry point main() (after the execution of the start-up code), and it will be executing in a default thread that's been created. So, every program will have at least one thread of execution. During the execution of the program, an arbitrary number of threads can be created through a standard library or platform-specific libraries. These threads can run in parallel if the CPU cores are available to execute them. If the number of threads are more than the number of CPU cores, even though there is parallelism, we cannot run all of the threads simultaneously. So, thread switching happens here as well. A program can launch any number of threads from the main thread, and those threads run concurrently on the initial thread. As we can see, the initial function for a program thread is main(), and the program ends when the main returns from its execution. This terminates all the parallel threads. Therefore, the main thread needs to wait...