Errata
The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
Version | Location | Description | Submitted by | Date Submitted |
---|---|---|---|---|
Page p. 156 and 157 of Design Patterns - Second Edition "UML" schema |
In my opinion, Client is not "composed" with the interfaces AbstractProductA and AbstractProductB? |
Claude Lepère | Apr 16, 2024 | |
Printed | Page 2nd ed, page 198 and all similar throughout book All annotations, done in what is supposed to look handwritten notes. |
(2nd edition, December 2020) |
Alan McGhee | Aug 05, 2022 |
Printed | Page 641 public interface Quackable "extends" QuackObserable" |
QuackObservable is an interface but we are extending it like a abstract class |
Maurice Lichtenberg | Mar 02, 2021 |
Printed | Page 95 last paragraph |
I'm having trouble understanding why class CondimentDecorator is implemented the way it is: |
Jochen Comes | Jan 02, 2021 |
Printed | Page 92 Diagram |
Same as for diagram on page 91: CondimentDecorator class has instance variable component, whereas Milk, Mocha, Soy, Whip classes have instance variable beverage. The latter is superfluous, Milk, Mocha, Soy, Whip should use component. |
Jochen Comes | Jan 02, 2021 |
Printed | Page 91 Diagram |
Both, the Decorator class and the ConcreteDecoratorA/ConcreteDecoratorB classes have an own/different instance variable for the component they decorate: Decorator has component and ConcreteDecoratorA/ConcreteDecoratorB have wrappedObj. |
Jochen Comes | Jan 02, 2021 |
Printed | Page 377 comments on the stack.peek() method |
The comments on the stack.peek() (2 places on the same page, one in next() method, the other in hasNext() method) says '...we get the current iterator off the stack...', peek() method DOES NOT remove the element from the collection. It's simply just getting the element. |
Ivy Chang | Nov 03, 2016 |
Printed | Page 369 method hasNext |
You don't need recursion here. In fact, if you use a while loop the code is a lot |
Anonymous | |
Printed | Page 374 CompositeIterator |
CompositeIterator bug, see also: |
Anonymous |