Book Image

Hands-On System Programming with C++

By : Dr. Rian Quinn
Book Image

Hands-On System Programming with C++

By: Dr. Rian Quinn

Overview of this book

C++ is a general-purpose programming language with a bias toward system programming as it provides ready access to hardware-level resources, efficient compilation, and a versatile approach to higher-level abstractions. This book will help you understand the benefits of system programming with C++17. You will gain a firm understanding of various C, C++, and POSIX standards, as well as their respective system types for both C++ and POSIX. After a brief refresher on C++, Resource Acquisition Is Initialization (RAII), and the new C++ Guideline Support Library (GSL), you will learn to program Linux and Unix systems along with process management. As you progress through the chapters, you will become acquainted with C++'s support for IO. You will then study various memory management methods, including a chapter on allocators and how they benefit system programming. You will also explore how to program file input and output and learn about POSIX sockets. This book will help you get to grips with safely setting up a UDP and TCP server/client. Finally, you will be guided through Unix time interfaces, multithreading, and error handling with C++ exceptions. By the end of this book, you will be comfortable with using C++ to program high-quality systems.
Table of Contents (16 chapters)

Chapter 7

  1. new() allocates a single object, while new() allocates an array of objects.
  2. No.
  3. Global memory is visible to the entire program, while static memory (defined globally) is only visible to the source file in which it is defined.
  4. By leveraging an alias with the alignas() function, such as using aligned_int alignas(0x1000) = int;.
  1. Not in C++17 and below
  2. std::shared_ptr should only be used if more than one object must own the memory (that is, the memory needs to be able to be released by more than one object in any order and at any time).
  3. Yes (depending on the operating system and permissions).
  4. If you allocate 4 bytes and use 3, you have created internal fragmentation (wasted memory). If you allocate memory in such a way that the allocator no longer has contiguous blocks of memory to give out (even if it has a lot of free memory), you have created external fragmentation...