Chapter 12. Multi-threaded Programming
- Table of Contents
- SDL_CreateThread — Creates a new thread of execution that shares its parent's properties.
- SDL_ThreadID — Get the 32-bit thread identifier for the current thread.
- SDL_GetThreadID — Get the SDL thread ID of a SDL_Thread
- SDL_WaitThread — Wait for a thread to finish.
- SDL_KillThread — Gracelessly terminates the thread.
- SDL_CreateMutex — Create a mutex
- SDL_DestroyMutex — Destroy a mutex
- SDL_mutexP — Lock a mutex
- SDL_mutexV — Unlock a mutex
- SDL_CreateSemaphore — Creates a new semaphore and assigns an initial value to it.
- SDL_DestroySemaphore — Destroys a semaphore that was created by SDL_CreateSemaphore.
- SDL_SemWait — Lock a semaphore and suspend the thread if the semaphore value is zero.
- SDL_SemTryWait — Attempt to lock a semaphore but don't suspend the thread.
- SDL_SemWaitTimeout — Lock a semaphore, but only wait up to a specified maximum time.
- SDL_SemPost — Unlock a semaphore.
- SDL_SemValue — Return the current value of a semaphore.
- SDL_CreateCond — Create a condition variable
- SDL_DestroyCond — Destroy a condition variable
- SDL_CondSignal — Restart a thread wait on a condition variable
- SDL_CondBroadcast — Restart all threads waiting on a condition variable
- SDL_CondWait — Wait on a condition variable
- SDL_CondWaitTimeout — Wait on a condition variable, with timeout
SDL provides functions for creating threads, mutexes, semphores and condition variables.
In general, you must be very aware of concurrency and data integrity issues when writing multi-threaded programs. Some good guidelines include:
-
Don't call SDL video/event functions from separate threads
-
Don't use any library functions in separate threads
-
Don't perform any memory management in separate threads
-
Lock global variables which may be accessed by multiple threads
-
Never terminate threads, always set a flag and wait for them to quit
-
Think very carefully about all possible ways your code may interact
Note: SDL's threading is not implemented on MacOS, due to that lack of preemptive thread support (MacOS X dos nt suffer from this problem)