kc3-lang/libevent /evthread.c

Branch :

Log

Author	Commit	Date	CI	Message
	743f8665	2010-08-23 11:48:46		Honor NDEBUG; build without warnings with NDEBUG; make NDEBUG always-off in unit test code
	d4977b52	2010-08-17 13:15:34		Add a condition variable backend, with implementations for pthreads and win32 The interface from the user's POV is similar to the locking implementation: either provide a structure full of function pointers, or just call evthread_use__threads() and everything will be okay. The internal interface is meant to vaguely resemble pthread_cond_, which Windows people will better recognize as ConditionVariable.
	3808168d	2010-08-10 15:02:50		Completely remove the (mostly-removed) obsolete thread functions.
	ec347b92	2010-07-07 16:45:03		Move event-config.h to include/event2 This change means that all required include files are in event2, and all files not in event2/* are optional.
	c5bab560	2010-05-11 11:44:07		Remove the obsolete evthread interfaces These were added in 2.0.1, and deprecated in 2.0.4 and 2.0.5; we've promised that they would be removed, and warned whenever they were invoked. Users should call evthread_set_lock_callbacks instead... or ideally just call evthread_use_windows_threads or evthread_use_pthreads.
	17efc1cd	2010-03-04 01:25:51		Update all our copyright notices to say "2010"
	e5bbd40a	2010-02-18 17:41:15		Clean up formatting: use tabs, not 8-spaces, to indent.
	c51bb3c3	2009-12-21 16:36:40		Fix a few locking issues on windows.
	0cd3bb9f	2009-11-27 17:22:19		Improved optional lock debugging. There were a couple of places in the code where we manually kept lock counts to make sure we never accessed resources without holding a lock, and that we never released a lock we didn't have. The lock-debugging code already puts counts on _every_ lock when lock debugging is enabled, so there is no need to keep these counts around otherwise. This patch rewrites the ASSERT_FOO_LOCKED macros to all use a common EVLOCK_ASSERT_LOCKED(). We also teach the lock debugging code to keep track of who exactly holds each lock, so that EVLOCK_ASSERT_LOCKED() means "locked by this thread."
	76cd2b70	2009-11-27 16:44:47		Stop passing EVTHREAD_READ and EVTHREAD_WRITE to non-rw locks. Previously, our default lock model kind of assumed that every lock was potentially a read-write lock. This was a poor choice, since read-write locks are far more expensive than regular locks, and so the lock API should only use them when we can actually take advantage of them. Neither our pthreads or win32 lock implementation provided rw locks. Now that we have a way (not currently used!) to indicate that we really want a read-write lock, we shouldn't actually say "lock this for reading" or "lock this for writing" unless we mean it.
	347952ff	2009-11-27 15:20:43		Revise the locking API: deprecate the old locking callbacks and add trylock. Previously, there was no good way to request different kinds of lock (say, read/write vs writeonly or recursive vs nonrecursive), or for a lock function to signal failure (which would be important for a trylock mode). This patch revises the lock API to be a bit more useful. The older lock calls are still supported for now. We also add a debugging mode to catch common errors in using the locking APIs.