Gain insights into software design patterns and architecture in C++. Learn about C++ idioms, concurrency patterns, and apply the right solutions to improve code quality and productivity.

Design Pattern and Architectural Pattern with C__.png

cpp.tar.gz

Thread_sanitizer

Thread_sanitizer-copy

Thread_sanitizer-copy-copy

reactor

Software engineering researchers and practitioners noticed that parts of software projects could often be solved using approaches that were discovered earlier to solve similar problems. This led to the documentation of software design and architectural patterns, which are known solution approaches to a class of problems. 

This course starts by putting software patterns into perspective by answering the question, “What is a software pattern, and how is it different from an algorithm?” You will then learn about the two classes of patterns—software design and architecture patterns. Next, you’ll learn common C++ idioms. Finally, you will learn about software patterns for concurrency. 

By the end of the course, you will have useful and practical tools to improve the quality of your code and productivity. You’ll also be able to analyze a given part of your software project, pick the right pattern for the job, and apply it.

Master Software Design Patterns and Architecture in C++

#include <iostream>
#include <string>
#include "public.h"

class PublicClass::PImplClass {
 public:
    void DoPrivateStuff() {
        std::cout << className << "::privateMethod\n";
    }
 private:
    std::string className = "PublicClass";
};

PublicClass::PublicClass(): pImpl(new PImplClass) {}
PublicClass::~PublicClass() = default;

void PublicClass::publicMethod() {
    std::cout << "PublicClass::publicMethod\n";
    pImpl->DoPrivateStuff();
}

#include <memory>

class PublicClass {
 public:
    PublicClass();
    ~PublicClass();
    void publicMethod();
 private:
    class PImplClass;
    std::unique_ptr<PImplClass> pImpl;
};

#include "public.h"

int main() {

    PublicClass pub;
    pub.publicMethod();

}

# Code explanation 

- **`public.h`** file:
  - **Lines 5–7:** We already declared three `public` methods in the `PublicClass`: Constructor, Destructor, and a `publicMethod`. In this public method, we will access the implementation class `DoPrivateStuff()`.
  - **Lines 9–10:** We defined the `pImpl` (opaque pointer) of the `PImplClass`.
- **`public.cpp`** file:

   - **Lines 5–12:** We defined the `PImplClass` that will do the implementation of the `PublicClass`. We initialized a `DoPrivateStuff()` (implementation of Public class) and a private `className` variable. This method will interact with private data members of its class; hence it has been given the name `DoPrivateStuff()`. However, it should be made public so that the public method can access it.
  - **Lines 14–15:** We defined the constructor and destructor of the `PublicClass`. In the constructor, we initialized the `pImpl` pointer. 
  - **Lines 17–20:** In the public method, we will call the PImpl class's `DoPrivateStuff()` (implementation of Public class) with the help of the `pImpl` pointer.

In the example above, any changes made in the PImpl class will be restricted to that class. We need to recompile the Public class in case we want to change an implementation detail, which can now be made in the PImpl class.


Get a detailed explanation of the solution to the PImpl exercise.

Introduction

Introduction to Design Patterns

Deep Dive into Design Patterns

More Design Patterns

Idioms

Architectural Patterns

Patterns for Concurrency

Conclusion

Solution: PImpl Idiom

Solution

Code explanation