Errata

Objective-C Pocket Reference

Errata for Objective-C Pocket Reference

Submit your own errata for this product.

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
Printed Page 10
2nd paragraph

The text says "ec@class declaration" instead of "@class declaration". Should also have a reference to the "Forward Declarations" section for further clarification.

 Anonymous  May 28, 2008 
Printed Page 10
2nd paragraph

This was a known previous error and is stated in the posted errata on the website, but a little different:

My books says:
c@class

When it should say:
@class

Previously there was an extra 'e' that was fixed:
ec@class

Marc.
mrdat222@yahoo.com

 Marc Weintraub  Apr 28, 2009 
Printed Page 15
second bullet from the bottom of the page

"If the object inherits from the receiver's class, the field is not visible."
I believe the word 'not' is erroneous here. A field that is declared as @protected
can be accessed from this class and any class which inherits from it.

 Anonymous   
Printed Page 15
second bullet from the bottom of the page

"If the object inherits from the receiver's class, the field is not visible."
I believe the word 'not' is erroneous here. A field that is declared as @protected
can be accessed from this class and any class which inherits from it.

 Anonymous   
Printed Page 22
Line 9 of code, top of page

The return value of the "top" method should calculate the top value as

[center y] + radius

not

[center y] - radius

This assumes normal Cartesian co-ordinates where y increases from bottom to top.

 Mac MacLaren  Oct 20, 2009 
Printed Page 38
In section "Forward Declarations"

When describing the compiler directives for forward declarations, both "@class ClassName" and "@protocol ProtocolName" should have semicolons after them. (The @class directive is used correctly in the sample code below.)

 Anonymous   
Printed Page 38
In section "Forward Declarations"

When describing the compiler directives for forward declarations, both "@class ClassName" and "@protocol ProtocolName" should have semicolons after them. (The @class directive is used correctly in the sample code below.)

 Anonymous  May 28, 2008 
Printed Page 39
first paragraph

"complier" should read "compiler"

 Mac MacLaren  Nov 02, 2009 
Printed Page 58
text of the "NOTE"

This is either confusing or an error. If it refers to the snippet above, it should
say

"Descendents of NSObject will use -dealloc instead of -free."

 Anonymous   
Printed Page 58
text of the "NOTE"

This is either confusing or an error. If it refers to the snippet above, it should
say

"Descendents of NSObject will use -dealloc instead of -free."

 Anonymous   
Printed Page 65
Item 5 in the numbered list

Typo in text:

"Both Object and NSObject provides ..."

should be:

"Both Object and NSObject provide ..."

 Anonymous  May 28, 2008 
Printed Page 73
First 2 bullets

Since the -superClass method returns a Class, it would seem that it should return "Nil" rather than "nil", as discussed on page 65.

 Anonymous   
Printed Page 73
First 2 bullets

Since the -superClass method returns a Class, it would seem that it should return "Nil" rather than "nil", as discussed on page 65.

 Anonymous  May 28, 2008 
Printed Page 90
2nd full paragraph

Should change "train of events" to "chain of events".

 Anonymous   
Printed Page 90
2nd full paragraph

Should change "train of events" to "chain of events".

 Anonymous  May 28, 2008