Re: There's obviously something I don't understand about autorelease.
Re: There's obviously something I don't understand about autorelease.
- Subject: Re: There's obviously something I don't understand about autorelease.
- From: Matt Neuburg <email@hidden>
- Date: Mon, 19 Mar 2012 11:48:50 -0700
On Sat, 17 Mar 2012 21:06:49 -0700, Quincey Morris <email@hidden> said:
>I shouldn't have suggested that property declarations didn't need memory management attributes, but all of the current attributes are "wrong" (because they do double-duty as ivar reference attributes). I *think* the "right" property attributes should be exactly one of the following list per declaration:
>
> owning
> nonowning
> copying
> readonly
> readwrite,owning
> readwrite,nonowning
> readwrite,copying
>
As long as we're just dreaming up our own linguistic world, I'd suggest that instead of "owning" we say "owning-copying". I've never liked the way "copy" implies "retain". The word "retain" tells you something very important, namely that this thing has an elevated retain count and needs release later. It's not very nice to expect a beginner to know that "copy" *also* means that. If you're copying, you're taking ownership, and "owning-copying" would remind you of that. m.
--
matt neuburg, phd = email@hidden, <http://www.apeth.net/matt/>
A fool + a tool + an autorelease pool = cool!
Programming iOS 5! http://shop.oreilly.com/product/0636920023562.do
_______________________________________________
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