Ryan C. Gordon 899eb0d042 thread: Locking mutexes and rwlocks are now void functions. ... Almost nothing checks these return values, and there's no reason a valid lock should fail to operate. The cases where a lock isn't valid (it's a bogus pointer, it was previously destroyed, a thread is unlocking a lock it doesn't own, etc) are undefined behavior and always were, and should be treated as an application bug. Reference Issue #8096.		2023-10-26 08:57:34 -04:00
..
SDL_syscond.cpp	Rename SDL mutex, semaphore and condition variable types to match SDL 3.0 naming convention	2023-04-28 12:08:33 -07:00
SDL_sysmutex.cpp	thread: Locking mutexes and rwlocks are now void functions.	2023-10-26 08:57:34 -04:00
SDL_sysmutex_c.h	Rename SDL mutex, semaphore and condition variable types to match SDL 3.0 naming convention	2023-04-28 12:08:33 -07:00
SDL_sysrwlock.cpp	thread: Locking mutexes and rwlocks are now void functions.	2023-10-26 08:57:34 -04:00
SDL_systhread.cpp	Fix remaining typos (#7921)	2023-07-03 12:46:47 -07:00
SDL_systhread_c.h	Updated copyright for 2023	2023-01-09 09:41:41 -08:00