Book Image

Boost C++ Application Development Cookbook - Second Edition

By : Anton Polukhin Alekseevic
Book Image

Boost C++ Application Development Cookbook - Second Edition

By: Anton Polukhin Alekseevic

Overview of this book

If you want to take advantage of the real power of Boost and C++ and avoid the confusion about which library to use in which situation, then this book is for you. Beginning with the basics of Boost C++, you will move on to learn how the Boost libraries simplify application development. You will learn to convert data such as string to numbers, numbers to string, numbers to numbers and more. Managing resources will become a piece of cake. You’ll see what kind of work can be done at compile time and what Boost containers can do. You will learn everything for the development of high quality fast and portable applications. Write a program once and then you can use it on Linux, Windows, MacOS, Android operating systems. From manipulating images to graphs, directories, timers, files, networking – everyone will find an interesting topic. Be sure that knowledge from this book won’t get outdated, as more and more Boost libraries become part of the C++ Standard.
Table of Contents (19 chapters)
Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Syncing interprocess communications


In the previous recipe, we saw how to create shared memory and how to place some objects in it. Now, it's time to do something useful. Let's take an example from the Making a work_queue recipe in Chapter 5, Multithreading, and make it work for multiple processes. At the end of this example, we'll get a class that may store different tasks and pass them between processes.

Getting ready

This recipe uses techniques from the previous one. You will also need to read the Making a work_queue recipe in Chapter 5, Multithreading, and get its main idea. The example requires linking against the runtime library rt on some platforms.

How to do it...

It is considered that spawning separate sub-processes instead of threads makes a program more reliable, because termination of a sub-process does not terminate the main process. We won't argue with that assumption here, and just see how data sharing between processes can be implemented.

  1. A lot of headers are required for this...