• 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: Synchronizing Thread Execution
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Synchronizing Thread Execution


  • Subject: Re: Synchronizing Thread Execution
  • From: leenoori <email@hidden>
  • Date: Tue, 5 Dec 2006 15:48:57 +0100

El 5/12/2006, a las 15:20, Scott Ribe escribió:

@synchronized does not interact with the object
in any way, doesn't send it any messages, at least as far as I know,
so why would it have to be initialized?

You may be right about that, but nil is still not a good idea...

Indeed, you're right. It was pointed out to me that the value of the pointer, not the location of the variable holding the pointer, is what matters; otherwise @synchronized (self) would be meaningless.


So @synchronized (nil) or @synchronized (variableThatIsSetToNil) *might* work in some way, but it won't do what I was thinking it did...

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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: 
 >Re: Synchronizing Thread Execution (From: Scott Ribe <email@hidden>)

  • Prev by Date: Re: Synchronizing Thread Execution
  • Next by Date: Sub classing.
  • Previous by thread: Re: Synchronizing Thread Execution
  • Next by thread: Re: Synchronizing Thread Execution
  • Index(es):
    • Date
    • Thread