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 (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
