On Saturday 13 April 2002 02:59 pm, David T. Lewis wrote:

> I'm calling #signalSemaphoreWithIndex: from the non-main thread,
> and that probably is the problem. But I have not yet thought of a
> way around this. The thread that waits on the read to complete is
> the one that needs to tell Squeak that the read has completed, but
> it presumably needs to be able to signal a Squeak semaphore as an
> atomic operation without being interrupted by the Windows
> scheduler. Otherwise, I imagine that it's possible for Squeak to go
> off and do an garbage collect right in the middle of a
> #signalSemaphoreWithIndex, which would probably not be a good
> thing.

Look at  synchronizedSignalSemaphoreWithIndex() in sqWin32Window.c. 
I'm not sure, but it looks like that's already set up for this kind 
of activity. Andreas should be able to answer this.

-- 
Ned Konz
http://bike-nomad.com
GPG key ID: BEEA7EFE