• 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: Understanding property/synthesize
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Understanding property/synthesize


  • Subject: Re: Understanding property/synthesize
  • From: Stefan Nobis <email@hidden>
  • Date: Thu, 12 Aug 2010 11:34:26 +0200
  • Mail-followup-to: Quincey Morris <email@hidden>, cocoa-dev <email@hidden>

Quincey Morris <email@hidden> writes:

> The ability to omit the instance variable (called the "non-fragile
> instance variable" mechanism) is a feature of the latest Objective-C
> compilers and runtime, and is available for 64-bit Mac OS x64
> applications, and applications running on an iOS device.

As I observed, omitting instance variables in class declarations is
also not very well supported by the (current) debugger. So even if
backwards compatibility is of no concern, it is still a good idea to
declare the instance variables explicitly in oder to get better
debugging support.

--
Until the next mail...,
Stefan.

Attachment: pgpyZTeWUr8R5.pgp
Description: PGP signature

_______________________________________________

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: 
 >Understanding property/synthesize (From: Stefan Nobis <email@hidden>)
 >Re: Understanding property/synthesize (From: Quincey Morris <email@hidden>)

  • Prev by Date: Re: What font do you use?
  • Next by Date: Re: Handling NSManagedObjectContextDidSaveNotification from different threads
  • Previous by thread: Re: Understanding property/synthesize
  • Next by thread: Problems with NSCell setObjectValue
  • Index(es):
    • Date
    • Thread