Re: Dumb ARC question
Re: Dumb ARC question
- Subject: Re: Dumb ARC question
- From: Rick Mann <email@hidden>
- Date: Fri, 28 Dec 2012 01:06:33 -0800
On Dec 28, 2012, at 0:59 , Quincey Morris <email@hidden> wrote:
> Huh? References aren't weak by default anywhere.
>
> Are you thinking of __usafe_unretained? That's not weak, just unmanaged by ARC, and it's the only ownership qualifier allowed by ARC for struct members that point to objects (and therefore highly unrecommended).
Yes, that's what I meant. They're both "weak" in the sense that neither causes a retain, right? A weak pointer doesn't cause a retain, does it?
> For your original problem, your description is consistent with ARC *not* being used to compile this source file. You can check that easily enough by putting:
>
>> mInputBuffer = [[NSMutableData data] retain];
>
> and verifying that the compiler says you can't do that when ARC is turned on.
Wow. Somehow, there's a -fno-objc-arc flag on that one file. It's possible I added it, but I only built this project a week ago, and have absolutely no memory of doing that. Not sure why I would.
My properties have "strong" keywords in them, which I thought wouldn't work if it were not ARC, but I guess the modern compiler allows the word (treats it as "retain"?).
Anyway, thank you, and sorry for the false alarm.
--
Rick
_______________________________________________
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