🚀 go-pugleaf

Someone was just trying to add sound to a BackSpace module and ran into a  
sneaky problem that has been discussed before but bears repeating.

usleep() is implemented via signals (a questionable strategy IMHO), and many of  
the soundkit functions surreptitiously use threads to keep the sound buffers  
full.  Signals and threads do not mix gracefully, and the sound thread may  
catch the signal that was supposed to wake up the usleep() function, hanging it  
forever.

The solution is to pick some waiting method that doesn't use signals; for  
example waiting on a mach port.

One easy way to do this is to wait for an event that will never be received  
with an appropriate timeout.  For example:

	NXEvent dummyEvent;

	[NXApp peekNextEvent:0 
		into:&dummyEvent 
		waitFor:timeout
		threshold: NX_MODALRESPTHRESHOLD];

Maybe this will keep someone from tearing one's hair out.

-sam

--
Opinions expressed herein are not those of my employer.  They're not even
mine.  There is water at the bottom of the ocean.  Hi Mom!