Design patterns for modern C++ (a series?)

[lefticus]

Books to reference:

• C++ Software Design
• Head First Design Patterns (Java)
• Design Patterns (Classic Gang-of-Four / Pre-ISO C++)
• Modern C++ Design
• Hands on Design Patterns with C++

[toRatnesh]

It will be much helpful if you try to teach these concepts with a project or select an open source project and then explain uses of these concepts in that project.

[fcolecumberri]

Maybe could be more appropriate for the [fill the blank].

[lefticus]

Maybe could be more appropriate for the [fill the blank].

In many ways I agree - series don't tend to do very well on C++ Weekly. But I've been trying to not make [fill in the blank] too much C++.

One huge advantage to [fill in the blank] is that I don't have a specific release schedule to maintain too.

[lefticus]

I have decided to go ahead and move this to [fill in the blank] so I can take more time developing it, and not have to fit it into the C++Weekly schedule.

[lefticus]

Reference based text book implementation of the observer pattern: https://compiler-explorer.com/z/MTdf55Y43

[lefticus]

Self registration with enable_shared_from_this cannot work https://compiler-explorer.com/z/sPbse6Yxs

[lefticus]

Separate registration with shared_ptr https://compiler-explorer.com/z/z51eW653c

[lefticus]

Auto registration and deregistration, with inheritance: https://compiler-explorer.com/z/qsjvh5WsT

[lefticus]

Generic reusable templated version: https://compiler-explorer.com/z/z5z9e9hEv

Do we need to handle the case where the provider can be destroyed before the observer? I don't think this is a normal use case to warrant the extra code necessary, but it can be implemented.