Re: Coding Standards For Objective C
Re: Coding Standards For Objective C
- Subject: Re: Coding Standards For Objective C
- From: Sherm Pendley <email@hidden>
- Date: Wed, 24 Nov 2004 16:27:13 -0500
On Nov 24, 2004, at 2:58 PM, Ricky Sharp wrote:
Also, for foo, should I really be calling the accessor everywhere
rather than having a local?
In general, it's a good idea to use accessors any time you need to do
more than a simple assignment.
One example when you have an ivar that's an object type. Generally,
when you assign it a new value, you retain the new value and
(auto)release the old value. Consistently using an accessor in that
case will isolate your memory management into one place, making it less
likely to have retain/release bugs, and easier to debug if it does.
Another example is threading. If you're using mutexes to coordinate
access to an ivar among multiple threads, it's not a bad idea to
isolate all of that mutex-related code into accessor methods.
sherm--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden