• 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: @property problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: @property problem


  • Subject: Re: @property problem
  • From: j o a r <email@hidden>
  • Date: Mon, 11 Feb 2008 14:53:40 -0800


On Feb 11, 2008, at 2:32 PM, Kyle Sluder wrote:

Also, you have not specified a memory management method in your
@property declaration, which you must do if you are not using garbage
collection.

It defaults to "assign." Declaring that for a BOOL would be (unnecessarily) redundant.

Not true for non-GC code (which is what I specified). The compiler will issue a warning if you do not explicitly declare a memory management model


It will only issue a warning for object properties, not for non-object properties.

j o a r


_______________________________________________

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: @property problem
      • From: "Kyle Sluder" <email@hidden>
References: 
 >@property problem (From: Randall Meadows <email@hidden>)
 >Re: @property problem (From: "Kyle Sluder" <email@hidden>)
 >Re: @property problem (From: Brian Christensen <email@hidden>)
 >Re: @property problem (From: "Kyle Sluder" <email@hidden>)

  • Prev by Date: Re: Pop-up NSMenu without NSPopUpButton
  • Next by Date: re: self = [super init] debate.
  • Previous by thread: Re: @property problem
  • Next by thread: Re: @property problem
  • Index(es):
    • Date
    • Thread