• 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: Weak link usage? @property?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Weak link usage? @property?


  • Subject: Re: Weak link usage? @property?
  • From: Scott Squires <email@hidden>
  • Date: Tue, 22 Jul 2008 07:12:21 -0700

Yes, I typed in the wrong word.   Link instead of reference.

My point being:

1. The compiler complains and states that 'assign' is incorrect for non-GC usage (if I don't explicitly state assign).
If i do use assign it doesn't complain but because it thinks assign is incorrect I wanted to verify it was ok instead of just a way to stop the compiler from complaining.


2.   Rules of when properties are used and when they aren't:
      [self setMyClass: myClassObject];
      self.myClass = myClassObject;
     myClass = myClassObject;


Since these all change the value of myClass it's certainly not obvious that the behavior itself should be different between them, especially if you're used to using C++ or when converting from previous Obj-C code.
Going through the documents in detail they do clarify this but I suspect it has caused a few bugs for people who might overlook these details.



_______________________________________________

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


  • Prev by Date: Re: webDAV (lite) framework?
  • Next by Date: Re: webDAV (lite) framework?
  • Previous by thread: Re: Weak link usage? @property?
  • Next by thread: set posterImage in QTKit?
  • Index(es):
    • Date
    • Thread