Comments on: Coding Conventions: iVars

By: Jonathan Lundell

Jonathan Lundell — Fri, 15 Jul 2011 01:02:00 +0000

Why declare your ivars in @interface at all? Clients should use the property interface, and for the @implementation, the @synthesize declaration is adequate. Bonus: you don’t have to worry about the @interface and @synthesize names matchingâ€”eliminate one more possibility of error.

By: neil

neil — Thu, 14 Jul 2011 11:01:00 +0000

You have a typo in your description of “Overriding a setter”. In the code you call the argument newPostName, but in your description of the code you refer to it as newPostTitle.

By: Eireien

Eireien — Thu, 14 Jul 2011 07:43:00 +0000

Apple suggests to avoid using accessor methods in the -init: http://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/MemoryMgmt/Articles/mmPractical.html#//apple_ref/doc/uid/TP40004447-SW6

By: Nate Heagy

Nate Heagy — Wed, 13 Jul 2011 19:37:00 +0000

There is no reason to add the data member to theÂ @interface:disqusÂ
Â yourself. As written, you can deleteNSString *_postName;NSDate *_postDate;Author *_author;

and it will work just fine.

By: Collin

Collin — Wed, 13 Jul 2011 19:19:00 +0000

This is a good point, I have never run into a problem with it, but this could cause issues. Maybe we should switch to a suffix notation as well.

By: Collin

Collin — Wed, 13 Jul 2011 19:18:00 +0000

Added. Thansk!

By: navX

navX — Wed, 13 Jul 2011 19:05:00 +0000

And,…

Identifiers prefixed with underscores are reserved by Apple, so you don’t want to prefix your variables with an underscore. That’s why Google suggests using a suffix instead. FromÂ Apple’s Developer Guide:
Avoid the use of the underscore character as a prefix meaning private, especially in methods.Apple reserves the use of this convention. Use by third parties could result in name-space collisions; they might unwittingly override an existing private method with one of their own, with disastrous consequences. See â€œPrivate Methodsâ€ for suggestions on conventions to follow for private API.

,… so in your code might create conflicts with Cocoa…

I like the idea, but unfortunately can’t use it for big projects.

By: navX

navX — Wed, 13 Jul 2011 18:59:00 +0000

it needsÂ deallocÂ inÂ @implementation to be safe about memory management.