Re: multithreaded callbacks (was Re: [AD] de fourium pointium ohium)

[George Foot <gfoot@xxxxxxxxxx>]

On Fri, Jul 13, 2001 at 03:14:48PM +1000, Peter Wang wrote:
> (0) pause the main thread when timer (etc.) callbacks are running
...
> (0) is good because it means _all_ old DOS code ported to non-DOS
> platforms will still be correct.  Otherwise it's not very nice, and
> has problems associated with it.

Is it even possible in pthreads?

> (1 a) is my preference.  Personally I like the API Eric suggested
> (create_mutex, destroy_mutex, lock_mutex, unlock_mutex), which is
> much like the bitmap API.  Under platforms that don't need it, these
> functions would do nothing.

My feelings against this were mostly: why should we implement
yet another thread wrapper API?  It would be nice to just use
pthreads.  I guess it's unreasonable to expect people to have it
in Windows though.

We need to make it clear whether these are isolated and
independent of the timer implementation (so people can use other
mutex handling calls if they want to), or whether there's
interaction between these routines and other parts of Allegro
(in which case people must use these routines).

George

-- 
Random project update:
06/03/2001: AllegroGL 0.0.10 released at http://allegrogl.sourceforge.net/
	Six months' worth of changes, including Mingw32 support!