Thanks Greg! This really clears up a lot! And also thanks about
clarifying the bit about the objc->ivar syntax. Seems I jumped to
conclusions when I accidentally tried to access another object's ivar
that way.
Personally I think you're doing a great job with the GC, Dispatch and
Blocks support! These are extremely exciting times to be a Mac developer
and I am glad I made the switch.
Keep it up :)
André
--- Original Nachricht ---
Absender: Greg Parker
Datum: 03.10.2009 11:39 Uhr
(If you use the OSAtomic functions directly with GC-scanned storage,
then you can confuse the garbage collector which may delete your
objects unexpectedly.)
`obj->ivar` is perfectly legal, as long as you respect the ivar's
access permissions. You won't get a warning if you access the class's
own @private ivars, or its superclass's @protected ivars, or any other
class's @package or @public ivars.
_______________________________________________
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
