Errata

From APIDesign

(Difference between revisions)
Jump to: navigation, search
Line 15: Line 15:
Page 178: Type parameter is bit confusing. While most of the people are familiar with single uppercase letter (like ''T'', ''E'', ''V'') and can easily recognize them as a type parameter author is using ''Configuration'' and switch to ''C'' just a few lines later.
Page 178: Type parameter is bit confusing. While most of the people are familiar with single uppercase letter (like ''T'', ''E'', ''V'') and can easily recognize them as a type parameter author is using ''Configuration'' and switch to ''C'' just a few lines later.
 +
 +
== Chapter 11 ==
 +
Page 195 and 196: It would be nice for the samples to have a bit wider context. They may be too hard to understand.

Revision as of 12:13, 14 October 2008

Contents

Chapter 7

Page 123: For the sake of consistency with other samples and to teach reader to be defensive, lookup and ic fields should be final.

Chapter 8

Page 132: Implementation of Playback interface should be named MyPlaybackPrints instead of MyCallbackPrints.

Page 134: There should be append method mentioned (instead of write) in this sentence: "This is reasonable behavior for implementors because those who subclassed Writer have not implemented the new write method."

Chapter 10

Page 160: Introducing the String class in re-export sample is bit artificial and decreases readability. At least it should be renamed to something like LibraryString.

Page 160: There suddenly appears the Query library in the text not being introduced anywhere. Don't get confused. The only important thing to know about this library is that it is returning the re-exported String on computeReply() method call.

Page 164: The text is unfortunately silently referring to the "gray box" story (code completion). So when you read the text first and the NetBeans stories later you can get confused slightly.

Page 178: Type parameter is bit confusing. While most of the people are familiar with single uppercase letter (like T, E, V) and can easily recognize them as a type parameter author is using Configuration and switch to C just a few lines later.

Chapter 11

Page 195 and 196: It would be nice for the samples to have a bit wider context. They may be too hard to understand.

Personal tools
buy