• 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
How to use NSLock
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

How to use NSLock


  • Subject: How to use NSLock
  • From: "Peter Karlsson" <email@hidden>
  • Date: Sun, 2 Jan 2005 10:22:04 +0100

Dear list!

Can some please explain how I use NSLock to protect a variable from being
used or destroyed by another thread?

My app have 2 threads and a readProc. The normal thread that is always
there and a second thread that starts when I want to request a sysex dump
from my synthesizer.

The variable 'sysexcounter' is used in 2 places.

1 - 'sysexcounter' is incremented In my readProc that get the MIDI bytes

2 - In my second thread my app waits for 'sysexcounter' to get a predefined
value that is the size of my sysex message before the code flow continues.

But it seems that something happens that makes 'sysexcounter' useless. So I
want to protect it from being used by 2 places at the same time. I think
that is the right way to explain my problem.

Best regards Peter

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: How to use NSLock
      • From: Brendan Younger <email@hidden>
    • Re: How to use NSLock
      • From: Clark Cox <email@hidden>
  • Prev by Date: Re: Cocoa Bindings and Structures
  • Next by Date: NSSliderCells in an NSTableView not playing ball with with drag and drop
  • Previous by thread: Re: Cocoa Bindings and Structures
  • Next by thread: Re: How to use NSLock
  • Index(es):
    • Date
    • Thread