On Jan 18, 2009, at 13:52, Mike Abdullah wrote:
You're overriding the method, so it is up to you to implement the
copying behaviour.
On 18 Jan 2009, at 21:19, Sandro Noel wrote:
Greetings.
This is probably a stupid question.
if i have a property declared as
@property (readwrite, copy) NSString *name;
if I override the -(void) setName(NSString*)value{}
The object that I get as value is it already a copy?
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.
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.
_______________________________________________
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
