prmr / designbook Goto Github PK

Just noticed a small typo on page 270 that I thought you might want to be made aware of:

It some cases, however, we want to be able to operate ...

Should probably read:

In some cases, however, we want to be able to operate ...

MemorizingDeck should have field named aDrawnCards not aCards

"At this point the only thing left it to put the poem together by assembling the
twelve verses."

Should be:

"At this point the only thing left is to put the poem together by assembling the
twelve verses."

Hello @prmr,

I wanted to let you know that there is missing a line break on line 7 of the code sample on page 234.

The code is still readable, but could be a quick fix in the next version. 😄

Hi prof @prmr ,

Just wanted to let you know on page 77, at the end of the Special values of an enumerated type bullet point, that:

although we have four ranks and 13 suits

Should probably be reversed, like so:

although we have 13 ranks and four suits

Cheers!

Missing ")" for

   return String.format("%s: %s (%d minutes", title(), extra(), time());

and missing : in problem description to be consistent with solution:

$TITLE$ [...] ($TIME$ minutes)

Currently, the book calls comparator.comparing, but comparator is the name of an instance that has not been constructed yet.

Comparator<Card> comparator =
comparator.comparing(Card::getSuit());

The correct code should be capitalized Comparator.comparing because comparing is a static method in the Comparator class.

Comparator<Card> comparator =
Comparator.comparing(Card::getSuit());

The following Java libraries are deprecated because of a lack of event richness:

• java.util.Observable
• java.util.Observer

Other libraries such as java.beans.PropertyChangeListener, java.beans.PropertyChangeSupport, java.util.concurrent.Flow are more versatile (and might be worth expanding on in class!).

Current version:

Fortunately, we saw how to deal with this situation with the Interface Segregation Principle (ISP, see Section 3.2).

Correction:

Fortunately, we saw how to deal with this situation with the Interface Segregation Principle (ISP, see Section 3.8).