Chris Robinson e240351d81 Use a semaphore to signal the event handler ...

Semaphores allow for semi-persistent signals, compared to a condition variable
which requires a mutex for proper detection. A semaphore can be 'post'ed after
writing some data on one thread, and another thread will be able to recognize
it quickly even if the post occured in between checking for data and waiting.

This more correctly fixes a race condition with events since the mixer
shouldn't be using mutexes, and arbitrary wake-ups just to make sure an event
wasn't missed was quite inefficient.

2018-02-01 18:20:14 -08:00

..

Include

Use a semaphore to signal the event handler

2018-02-01 18:20:14 -08:00

alAuxEffectSlot.c

Fix the effect slot limit check

2018-01-28 17:56:47 -08:00

alBuffer.c

Fix error reporting for resource generation

2018-01-27 20:04:21 -08:00

alEffect.c

Don't bother with a return value that's never used

2018-01-27 23:50:04 -08:00

alError.c

Rename EventLock to make it more clear it's protecting the callback

2018-01-30 12:34:25 -08:00

alExtension.c

Construct error messages using parameterized values

2018-01-25 15:59:59 -08:00

alFilter.c

Move some inline functions into a header instead of copying them

2018-01-27 21:16:24 -08:00

alListener.c

Add the printf-format attribute to alSetError

2018-01-25 23:52:09 -08:00

alSource.c

Move some inline functions into a header instead of copying them

2018-01-27 21:16:24 -08:00

alState.c

Rename EventLock to make it more clear it's protecting the callback

2018-01-30 12:34:25 -08:00

alThunk.c

Use atomic flags for the thunk array

2017-04-14 16:14:05 -07:00

event.c

Use a semaphore to signal the event handler

2018-02-01 18:20:14 -08:00

sample_cvt.c

Fix some 'may be used initialized' warnings

2018-01-23 16:03:06 -08:00