3 ms·
> … written with Smalltalk in mind… "Since we must eventually implement our designs, a design pattern also provides sample C++ and (sometimes) Smalltalk code t
by igouy 5y ago
> … written with Smalltalk in mind…
"Since we must eventually implement our designs, a design pattern also provides sample C++ and (sometimes) Smalltalk code to illustrate an implementation."
Chapter 1. Introduction. "Design Patterns: Elements of Reusable Object-Oriented Software"
https://www.google.com/books/edition/_/6oHuKQe3TjQC https://www.google.com/books/edition/_/6oHuKQe3TjQC
- thedracle 5y agoWhat's your point exactly? Did they have smalltalk in mind or not?
- igouy 5y agoI wouldn't say so: Two of the authors - Erich Gamma, John Vlissides - clearly had a background in C++. Ralph Johnson - clearly had a background in Smalltalk. Richard Helm - not enough information. They said -- "We chose Smalltalk and C++ for pragmatic reasons: Our day-to-day experience has been in these languages and they are increasingly popular." They said -- "Our patterns assume Smalltalk/C++-level language features…" So when the original Design Patterns book was written, which features did C++ have "that didn't come to Java or Python for almost a decade" ?
- thedracle 5y agoOkay... They knew of Smalltalk, and many of the design patterns were around smalltalk features. And as you pointed out one of the authors had a strong background in smalltalk, and they chose Smalltalk for examples presented in the book. In other words, they had smalltalk in mind. It wasn't like smalltalk was some alien language none of the authors had ever heard of, or wasn't the subject of the book in any way.
- igouy 5y agoIn their words, they had "Smalltalk and C++" in mind.