Re: Properties and memory management with overrides.
Re: Properties and memory management with overrides.
- Subject: Re: Properties and memory management with overrides.
- From: Ben Trumbull <email@hidden>
- Date: Sun, 18 Jan 2009 16:29:31 -0800
And (I assume, for the same reason) that since the property is by
default atomic, the override is also responsible for implementing any
actual atomic behavior.
That's true. Custom accessor methods should respect the property
attributes or the property attributes should reflect the behavior of
the accessor methods.
I mention this because (I'm embarrassed to admit) I never really
thought about this till yesterday. I *think* other design decisions
have made the atomic-ness irrelevant to any of the code I've written,
but now I need to go back and check, especially where Core Data is
involved.
Core Data @dynamic properties are always nonatomic, irrespective of
the property declaration.
Core Data explicitly, intentionally, and states in the documentation,
that you can have any property atomicity you want so long as it's
nonatomic.
- Ben
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden