• 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: A quick one: Passing a reference/pointer to NSString
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A quick one: Passing a reference/pointer to NSString


  • Subject: Re: A quick one: Passing a reference/pointer to NSString
  • From: Graham Cox <email@hidden>
  • Date: Wed, 23 Jul 2008 12:43:03 +1000

I know, the problem lies with the caller. But this approach is bad form in my view, and does require that you take more care to avoid leaks.

Graham


On 23 Jul 2008, at 12:19 pm, Ken Thomases wrote:

There's nothing about returning an object pointer by reference that's inherently prone to leaking.

_______________________________________________

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: A quick one: Passing a reference/pointer to NSString
      • From: Jeff Brown <email@hidden>
References: 
 >Re: A quick one: Passing a reference/pointer to NSString (From: Jeff Brown <email@hidden>)
 >Re: A quick one: Passing a reference/pointer to NSString (From: Graham Cox <email@hidden>)
 >Re: A quick one: Passing a reference/pointer to NSString (From: Ken Thomases <email@hidden>)

  • Prev by Date: Re: A quick one: Passing a reference/pointer to NSString
  • Next by Date: Re: A quick one: Passing a reference/pointer to NSString
  • Previous by thread: Re: A quick one: Passing a reference/pointer to NSString
  • Next by thread: Re: A quick one: Passing a reference/pointer to NSString
  • Index(es):
    • Date
    • Thread