• 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: Unclear on -initWithBytesNoCopy:
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unclear on -initWithBytesNoCopy:


  • Subject: Re: Unclear on -initWithBytesNoCopy:
  • From: Charles Srstka <email@hidden>
  • Date: Mon, 05 Mar 2012 22:43:51 -0600

On Mar 5, 2012, at 6:40 PM, Wade Tregaskis wrote:

> Perhaps the only 'correct' solution to this problem is to fall back to the CFString level, where you can pass a custom CFAllocator to e.g. CFStringCreateWithBytesNoCopy().  That way the lifetime is effectively managed by the CFString, so it should behave correctly in all cases.

He’s using GNUstep, though. Does GNUstep even have the CFString level?

Charles
_______________________________________________

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


References: 
 >Unclear on -initWithBytesNoCopy: (From: Jens Alfke <email@hidden>)
 >Re: Unclear on -initWithBytesNoCopy: (From: Eli Bach2 <email@hidden>)
 >Re: Unclear on -initWithBytesNoCopy: (From: Wade Tregaskis <email@hidden>)

  • Prev by Date: Re: Unclear on -initWithBytesNoCopy:
  • Next by Date: Re: Unclear on -initWithBytesNoCopy:
  • Previous by thread: Re: Unclear on -initWithBytesNoCopy:
  • Next by thread: Re: Unclear on -initWithBytesNoCopy:
  • Index(es):
    • Date
    • Thread