Re: NSMutableDictionary autorelease chrashes application
Re: NSMutableDictionary autorelease chrashes application
- Subject: Re: NSMutableDictionary autorelease chrashes application
- From: "Michael Ash" <email@hidden>
- Date: Fri, 18 Jul 2008 15:49:40 -0400
On Fri, Jul 18, 2008 at 3:31 PM, Andy Lee <email@hidden> wrote:
> On Jul 18, 2008, at 2:59 PM, j o a r wrote:
>>
>> On Jul 18, 2008, at 11:51 AM, Andy Lee wrote:
>>>
>>> I don't see the difference from the caller's point of view.
>>
>>
>> There isn't any, and that was not MMalcs point. His point was that you
>> were using the term "autoreleased" incorrectly.
>
> I don't think I have ever said method X returns an autoreleased object. I
> was suggesting either the term could be accepted in the way that other
> people (and some Apple docs) use it, or someone could come up with a better
> term. There is a reason people keep using the term incorrectly, and it
> would be nice to help people express themselves without stumbling into the
> error.
I don't see any reason to use "autoreleased" in a situation where the
object in question has not, in fact, been sent the "autorelease"
method. It's just confusing.
The better term already exists: "own". As in, "you own the return
value" or "you do not own the return value". This tells you everything
you need to know.
Mike
_______________________________________________
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