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 14:36:37 -0700
On Mar 19, 2012, at 1:08 PM, Quincey Morris wrote:
> On Mar 19, 2012, at 11:48 , Matt Neuburg wrote:
>
>> 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.
>
> "you" == "the class implementor"??
I'm looking at it from the programmer's (esp. learner's) point of view in general. I'm just thinking of what would be a useful and expressive term, just as you were doing with "owning" in the first place. m.
--
matt neuburg, phd = email@hidden, http://www.apeth.net/matt/
pantes anthropoi tou eidenai oregontai phusei
Programming iOS 5! http://shop.oreilly.com/product/0636920023562.do
RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
TidBITS, Mac news and reviews since 1990, http://www.tidbits.com
_______________________________________________
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