Hi Daniel!

Thank you for asking!

1. Yes, I think it indeed violates SRP because both of these features can be implemented independently (at least, in many OOP languages).

2. Practically speaking, I personally don't care that much about following SRP. To me, SRP is just one of the indicators of the design. Still, as an author, I can't ignore this issue completely because I'd get backfire from the opposite camp. In any case, if I could do my thing efficiently while violating SRP, I would definitely do it. If it bites me in the future, I will refactor it away.

BTW, if anyone reading this topic wants to add something to the discussion, you're very welcome!

Thank you for your feedback!

Hi!

Sorry for the late reply. Maybe eventually I'll add C++ support, but it'll most likely happen in the far future.

The examples are currently in production. The current version is available at https://github.com/RefactoringGuru/design-patterns-dart

Hi!

If applicable, most of the patterns described in my book would contain one of the SOLID principles in the Pros & Cons section. At the same time, it was not my goal to view each pattern through the prism of SOLID. I only pointed out the most obvious features that stand out. I believe there might be no clear answer to your question. The patterns and the SOLID principles had been invented independently. But with a good understanding of the SOLID principles, you would be able to answer both questions—why some of the principles are relevant to a pattern, and why the rest aren't. 

Thank you! I'm glad that my book was to your liking!

Hi!

Most likely no, as the author (me) doesn't have any C++ experience.

Thank you, Gleb! I'm glad that you like it!

Hi!

Thanks for the idea! I haven't considered it yet.

Thanks for your feedback, Ryan! I'm glad that you liked the book.