• 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: if statement causing 32 Byte leak?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: if statement causing 32 Byte leak?


  • Subject: Re: if statement causing 32 Byte leak?
  • From: Dave Keck <email@hidden>
  • Date: Sat, 9 Jan 2010 15:40:45 -1000

> Discussion
> This method is a combination of alloc and init. Like alloc, it initializes the isa instance variable of the new object so it points to the class data structure. It then invokes the init method to complete the initialization process.

While we're on the topic, I always thought +new would be much more
useful if it did autorelease the result, making it inline with class
convenience constructors. Any specific reason why this isn't so?
_______________________________________________

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: if statement causing 32 Byte leak?
      • From: Andy Lee <email@hidden>
References: 
 >if statement causing 32 Byte leak? (From: "Mr. Gecko" <email@hidden>)
 >Re: if statement causing 32 Byte leak? (From: Paul Bruneau <email@hidden>)
 >Re: if statement causing 32 Byte leak? (From: "Mr. Gecko" <email@hidden>)
 >Re: if statement causing 32 Byte leak? (From: Graham Cox <email@hidden>)

  • Prev by Date: Re: if statement causing 32 Byte leak?
  • Next by Date: Re: if statement causing 32 Byte leak?
  • Previous by thread: Re: if statement causing 32 Byte leak?
  • Next by thread: Re: if statement causing 32 Byte leak?
  • Index(es):
    • Date
    • Thread