Thanks. Yeah maybe that's a better convention. I typically use _parameter for methods because I don't like putting _ivar in class definitions. I'd rather be able to do this:
size.width = _size.width; instead of the other way around. To me the ivars in a class are already private (unless they're exposed through a @property). So putting _ivar is like declaring private twice. I guess that's just always been my preference. For me it comes from working with java or actionscript, where you can declare an ivar as "private var something:String". So declaring "private var _something:String" is like saying "private private var something:String" oh well! On Wed, May 12, 2010 at 10:04 AM, Corbin Dunn <corb...@apple.com> wrote: >> - (void) setCornerSize:(NSSize) _size >> { >> [self willChangeValueForKey:@"cornerSize"]; >> [[self cell] setCornerSize:_size]; >> [self didChangeValueForKey:@"cornerSize"]; >> } > > > Just as a quick tip -- you might want to use a different formal parameter > name. Using the underscore prefix is typically done for ivars (and private > Apple methods). Someone reading this line: > > [[self cell] setCornerSize:_size]; > > might assume you were accessing an ivar, not a parameter. > > corbin > > > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/cocoa-dev/beingthexemplarylists%40gmail.com > > This email sent to beingthexemplaryli...@gmail.com > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com