• 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: NSString Class Instance Variables
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSString Class Instance Variables


  • Subject: Re: NSString Class Instance Variables
  • From: Graham Cox <email@hidden>
  • Date: Wed, 14 Oct 2009 10:45:52 +1100


On 14/10/2009, at 10:38 AM, Greg Parker wrote:

On 32-bit Mac, if you strip ivars from the header then other code cannot subclass that class. The compiler will put subclass and superclass ivars in the same place, leading to exciting data corruption bugs.

All system frameworks are honest about their ivars, because they need to support subclasses.



Yes, that makes perfect sense. I guess I was assuming that you would only be using a class 'as is', not subclassing it.

--Graham


_______________________________________________

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: NSString Class Instance Variables
      • From: Ariel Feinerman <email@hidden>
References: 
 >NSString Class Instance Variables (From: Richard Somers <email@hidden>)
 >Re: NSString Class Instance Variables (From: Graham Cox <email@hidden>)
 >Re: NSString Class Instance Variables (From: Greg Parker <email@hidden>)

  • Prev by Date: Re: Property List Format vs NSKeyedArchiver Format
  • Next by Date: Re: Property List Format vs NSKeyedArchiver Format
  • Previous by thread: Re: NSString Class Instance Variables
  • Next by thread: Re: NSString Class Instance Variables
  • Index(es):
    • Date
    • Thread