Yes, I typed in the wrong word. Link instead of reference.
My point being:
1. The compiler complains and states that 'assign' is incorrect for
non-GC usage (if I don't explicitly state assign).
If i do use assign it doesn't complain but because it thinks
assign is incorrect I wanted to verify it was ok instead of just a way
to stop the compiler from complaining.
2. Rules of when properties are used and when they aren't:
[self setMyClass: myClassObject];
self.myClass = myClassObject;
myClass = myClassObject;
Since these all change the value of myClass it's certainly not obvious
that the behavior itself should be different between them, especially
if you're used to using C++ or when converting from previous Obj-C
code.
Going through the documents in detail they do clarify this but I
suspect it has caused a few bugs for people who might overlook these
details.
_______________________________________________
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 [EMAIL PROTECTED]
