• 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: looking for a memory problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: looking for a memory problem


  • Subject: Re: looking for a memory problem
  • From: Shane Stanley <email@hidden>
  • Date: Thu, 19 Jul 2012 09:43:12 +1000

On 19/07/2012, at 1:35 AM, Sean McBride wrote:

> But you can prepare your code slowly, in a way that supports both.  ex:
> - replace all use of NSAllocateCollectable with malloc/free
> - change 'retain' to 'strong' in property declarations
> - replace CFMakeCollectable with CFBridgingRelease
> - replace NSMakeCollectable with a nil check and CFBridgingRelease

Thanks -- I didn't realize the last two.

So you are saying I can include things like __bridge and __bridge_retained in GC code, and they'll just be ignored until I flick the switch?

--
Shane Stanley <email@hidden>
'AppleScriptObjC Explored' <www.macosxautomation.com/applescript/apps/>


_______________________________________________

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: looking for a memory problem
      • From: Sean McBride <email@hidden>
References: 
 >looking for a memory problem (From: Martin Hewitson <email@hidden>)
 >Re: looking for a memory problem (From: Sean McBride <email@hidden>)
 >Re: looking for a memory problem (From: Shane Stanley <email@hidden>)
 >Re: looking for a memory problem (From: Sean McBride <email@hidden>)

  • Prev by Date: Re: Icon Overlay on Mac OSX
  • Next by Date: Re: KVG generic enough?
  • Previous by thread: Re: looking for a memory problem
  • Next by thread: Re: looking for a memory problem
  • Index(es):
    • Date
    • Thread