• 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: nonatomic vs atomic assign/retain
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: nonatomic vs atomic assign/retain


  • Subject: Re: nonatomic vs atomic assign/retain
  • From: Torsten Curdt <email@hidden>
  • Date: Tue, 06 Sep 2011 18:55:38 +0200

Thanks for all the input so far.

What's left for me to understand is why access to outlets could
possibly need synchronization. After all it's just the loading of the
NIB that is writing to the outlets. Given that access to the outlets
is only valid after a certain safe point (awakeFromNib) one could
consider outlets final/immutable and therefor synchronization should
not be required.

I guess if the NIB loading mechanism was multithreaded and would keep
state directly in the outlets it would somewhat make sense - I just
have a hard time picturing it was implemented that way. Anyway - since
we don't have the source code this is all guessing and we probably
should just stick to the Memory Management Programming Guide ...but it
would be super nice if someone from Apple could fill in the "why".

cheers,
Torsten
_______________________________________________

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: nonatomic vs atomic assign/retain
      • From: Scott Ribe <email@hidden>
References: 
 >nonatomic vs atomic assign/retain (From: Torsten Curdt <email@hidden>)
 >Re: nonatomic vs atomic assign/retain (From: Thomas Davie <email@hidden>)
 >Re: nonatomic vs atomic assign/retain (From: Joar Wingfors <email@hidden>)

  • Prev by Date: Re: nonatomic vs atomic assign/retain
  • Next by Date: Re: The best way to call Cocoa methods not implemented in previous versions of the SDK?
  • Previous by thread: Re: nonatomic vs atomic assign/retain
  • Next by thread: Re: nonatomic vs atomic assign/retain
  • Index(es):
    • Date
    • Thread