• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Dumb ARC question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Dumb ARC question


  • Subject: Re: Dumb ARC question
  • From: Quincey Morris <email@hidden>
  • Date: Fri, 28 Dec 2012 00:59:21 -0800

On Dec 27, 2012, at 22:37, Rick Mann <email@hidden> wrote:

> So, the usual bit about references being weak by default in C structs (and C++ classes) doesn't hold here.

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).

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.



_______________________________________________

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

  • Follow-Ups:
    • Re: Dumb ARC question
      • From: Rick Mann <email@hidden>
References: 
 >Re: Dumb ARC question (From: Rick Aurbach <email@hidden>)
 >Re: Dumb ARC question (From: Rick Mann <email@hidden>)

  • Prev by Date: Re: Dumb ARC question
  • Next by Date: Re: Dumb ARC question
  • Previous by thread: Re: Dumb ARC question
  • Next by thread: Re: Dumb ARC question
  • Index(es):
    • Date
    • Thread