Errata for Head First Design Patterns

... that encourage woman to ... should be: ... that encourage women to ...

"trying to restoring" should be: "trying to restore"

runing should read: running

Items are numbered 1,2,3,5,..,10 instead of 1,2,3,4,5,..,10.

A space is missing between the word 'their' and the following opening parenthesis. So this: "...and the impact you've had on their(and our) lives is forever." should be: "...and the impact you've had on their (and our) lives is forever."

The string ".//" should be "//"

thruoghout should be: throughout

quack) should be quack()

... and Sqeak.java ... should be: ... and Squeak.java ...

The code is improperly indented, starting with the fourth line.

I'm flying with a rocket should be (in order to be consistent with the code at the bottom of the previous page): I'm flying with a rocket!

Master's second-to-last remark includes "maintaintability" it should be: maintainability

"Favor composition over inheritence" should be "Favor composition over inheritance"

The closing parenthesis is missing.

Minor layout booboo: missing "There are no Dumb Questions" heading

"CurrentConditions" should be "CurrentConditionsDisplay" (as it is in the code on p. 60). Also On page 56, the "subject" arrow from CurrentConditions (which should read CurrentConditionsDisplay) should point to the Subject interface, rather than WeatherData.

In the book and sample code for CurrentConditionsDisplay, the weatherData is created as "Subject weatherData". But in all other parts of the code not written in the book, it's written as "WeatherData weatherData" It doesn't seem to matter but surely one of them is the "more proper" way. And consistency would be nice.

Note from the Author or Editor:
Will get fixed in 2nd ed.

"There's so many different kinds of us Observers, there's no way you can anticipate everything we need." Should be: "There are so many different kinds of us Observers, there's no way you can anticipate everything we need."

Note from the Author or Editor:
Fixed in Updated Files/ for next printing

On page 64, the "subject" arrow from GeneralDisplay should point to Observable rather than WeatherData.

notifyObserver(arg) should read: notifyObservers(arg)

Instead of: so we've removed the code for register, add and notify it should be: so we've removed the code for register, remove and notify

Note from the Author or Editor:
Fixed in Updated Files/ for next printing.

Weatherdata weatherData = (WeatherData)observable; should not appear in the ForecastDisplay constructor, as it does now, but rather as the first line in the update() method.

would probably be wastefu). Following should be: would probably be wasteful). Following

remove extra "the" before "knowing the domain" ...in designing OOP systems and also a matter of the knowing the domain... should be: ...in designing OOP systems and also a matter of knowing the domain...

ConcereteDecoratorA and ConcereteDecoratorB should be: ConcreteDecoratorA and ConcreteDecoratorB

"The ConcreteDecorator has an instance variable for the thing it decorate.. should be: "The ConcreteDecorator has an instance variable for the thing it decorates."

the word "lotte" should be: "latte"

"Now that we don't need to worry about ..." should read just "We don't need to worry about ..."

"You can create the other three Beverage classes (DarkRoast, Decaf, Esperesso) in exactly the same way. should read: "You can create the other two Beverage classes (DarkRoast and Decaf) in exactly the same way.

It is write "to to" instead of "to" : Here, we're going to to pass the beverage ...

Note from the Author or Editor:
change: Here, we're going to to pass the beverage ... to: Here, we're going to pass the beverage ...

Both the cost() and getDescription() function notes say "first we delegate", however there is inconsistent ordering of the return syntax of the code (local value + delegated value in cost() vs. delegated value + local value in getDescription())

Note from the Author or Editor:
fixed in updated files/ for next printing

We're going to see a much better way of creating decorated objects when we cover the Factory and Builder Design Patterns. add to the existing annotation: Please note that the Builder Pattern is covered in the Appendix.

"specfic" should be: "specific"

At the end of the second Question paragraph, it says "which means it would not including Whip in the order." That should be "include" instead of "including."

The second sentence says "Say, I wanted my getDecription..." it should say: "Say, I wanted my getDescription..."

The last sentence says "Note that getDecription..." it should say: "Note that getDescription..."

There is a period missing at the end of the first line. "FileInputStream is the component that's being decorated The Java I/O..."

Note from the Author or Editor:
change: "FileInputStream is the component that's being decorated The Java I/O..." To: "FileInputStream is the component that's being decorated. The Java I/O..."

public float cost(){ should be: public double cost(){

"double mocha soy lotte with whip" should be: "double mocha soy latte with whip"

embarrasing -> embarrassing

pizza = new eggiePizza(); should be: pizza = new VeggiePizza();

a client of that object. Any time it needs a pizzam it asks should be: a client of that object. Any time it needs a pizza it asks

"But remember it also has the disadvanage..." should be: "But remember it also has the disadvantage..."

"write a class the implements ... should be "write a class that implements ...

line 3: There should be "nyStore.orderPizza" instead of "nyStore.order" line 6: There should be "chicagoStore.orderPizza" instead of "chicagoStore.order"

Erroneous space after first "thick".

"Grated Regiano cheese" should be: "Grated Reggiano Cheese" [in order to match the code shown on page 129]

The last sentence should start with 'They say "decide"'

framework that let's >> framework that lets

"different set that needs to shipped..." should be "different set that needs to be shipped..."

the seafood should be "Calamari", not "Camari"

Wrong way double-quotes

"...because I am used to create entire families..." should read: "...because I am used to creating entire families..."

"Subclasses are instaniated by the Factory Methods." It should be "Subclasses are instantiated by the Factory Methods."

depedent should be: dependent

"you'll see a it has a few issues later in the chapter". It should be "you'll see it has a few issues later in the chapter"

"fill" is rendered improperly (with a hard-to-read font)

statically inializing >> statically initializing

"setTemperaturet()" should read "setTemperature()"

Note from the Author or Editor:
Fixed in Updated Files/

"slot1 = Hottub" should read "slot1 == Hottub"

Note from the Author or Editor:
Fixed in updated files/

the word should be "perform", not "preform"

Sue's last sentence ends with a colon, but no example follows it. After the colon at the end of Sue's statement, add: "onCommands[0] = onCommand; offCommands[0] = offCommand; and so on for each of the seven command slots."

"(3) In the execute() method actions are invoked on the reciever." It should be: "(3) In the execute() method actions are invoked on the receiver."

"Home Automation of Bust" should be "Home Automation or Bust"

Printed:

Note from the Author or Editor:
Should replace "!!!!" with "?!"

"The Command Pattern decouples an object, making a request from the one that knows how to perform it." remove comma

"excute()" should be "execute()"

Replace RemoteControlTest with DuckTestDrive and remove newlines that are not in the code: %java DuckTestDrive The Turkey says... Gobble gobble I'm flying a short distance The Duck says... Quack I'm flying The TurkeyAdapter says... Gobble gobble I'm flying a short distance I'm flying a short distance I'm flying a short distance I'm flying a short distance I'm flying a short distance

")." should be ".)"

Spelling mistake: 'Enumaration'.

Note from the Author or Editor:
Enumaration -> Enumeration

"the second and forth steps are different, ..." should be "the second and fourth steps are different, ..."

"Tea needs to define brew() and addCondiments() — the two abstract methods from Beverage." Should it be "from CaffeineBeverage"?

Note from the Author or Editor:
Yes, it should! Fixed in Updated Files/

"a condiments" should be "condiments"

"so you can implement these as hooks rather than abstract classes," It should be: "so you can implement these as hooks rather than abstract methods,"

"Subclasses decide which concrete classes to create." It should be: "Subclasses decide which concrete classes to instantiate."

"paired" should be "pared"

is used by the tempate -> is used by the template

Missing terminating period

"...you'll need to call the getMenuItem() method ..." should be: "...you'll need to call the getMenuItems() method ..."

Improper facing closing double-quotes

Items are lettered A, B, C, C, D, E. Should be A, B, C, D, E, F. [328 + 330] 1st paragraph, 2nd sentence; The "getIterator()" text on pages 328 and 330 (first paragraph, both pages) should be replaced with "createIterator()"

you'llwant should read: you'll want

"Could I implement an Iterator that can go backwards as well as backwards?" should be: "... backwards as well as forwards?"

second to the last line of paragraph: "... chefs that the time as come for us..." should be "... chefs that the time has come for us..."

"icecream" should be "ice cream"

Text states: "We also need two top level menu now that we'll name allMenus." Corrected Version: "We also need a top level menu that we'll name all Menus."

"icecream" should be "ice cream"

Hashtable and ArrayList both implement this interface. Should be: ArrayList implements this interface.

Replace the text "State Pattern" at the top left of the diagram with "Strategy Pattern", and replace the description on the bottom right of the page, "Allows an object to change its behavior when some state changes" with "Encapsulates interchangeable behaviors and uses delegation to decide which one to use."

Items are lettered A, B, C, C, D, E. Should be A, B, C, D, E, F.

In the last sentence of the paragraph you're writing about having to implement an "empty gumball condition" I think this should be an "empty gumballmachine condition"

Note from the Author or Editor:
fixed in Updated Files/

A comma is missing after "methodology".

Items are lettered A, B, C, C, D, E. Should be A, B, C, D, E, F.

"I wonder if this will this make it easier to add new states?" It should be: "I wonder if this will make it easier to add new states?"

The last sentence says "not to mention that CEO will drive us crazy." I'm not sure since English is not my native language, but I think this should be something like "not to mention that the CEO will drive us crazy."

Note from the Author or Editor:
changed to "the CEO" in Updated Files/

First sentence: "Now we're going put all the behavior..." should be: "Now we're going to put all the behavior..."

Currently: The only requirement is that your state objects do not keep their own internal state; ... I think the last this should be: Currently: The only requirement is that your state objects do not keep their own internal context; ...

Note from the Author or Editor:
fixed in updated files/

Items are lettered A, B, C, C, D, E. Should be A, B, C, D, E, F.

Improper facing double-quotes

The word "rmiregistery" should be "rmiregistry".

>hand-deliver the these

Note from the Author or Editor:
change: hand-deliver the these to: hand-deliver these

"Note that this can be slightly dangerous if you try to access this field once its been serialized and transferred." Should be: "Note that this can be slightly dangerous if you try to access this field once it's been serialized and transferred."

"If they were coupled the client would have to wait until each image is retrieved before it could paint it entire interface." should be: "If they were coupled the client would have to wait until each image is retrieved before it could paint its entire interface."

Second sentence should read "Let's update the simulator and give it a try:" not "...give it try:"

"applications" should be "application's"

"repititious" should be "repetitious"

interface of the HeatModel should be interface of the HeartModel.

Note from the Author or Editor:
Fixed in Updated Files/

minor typo: "and displayed in a seb browser." should be "and displayed in a web browser."

"...I understand each classes’ role." Should be: "....I understand each class's role."

Note from the Author or Editor:
Fixed for next printing (UpdatedFiles/)

"Ensures one and only object is created." Was probably meant to read: "Ensures one and only one object is created." This is repeated in the exercise's solution on page 610.

Note from the Author or Editor:
Fixed in Updated Files/ for next printing

Improper facing single quote to the right of the left parenthesis.

repetition ::= ... <expresion> should be <expression>