Re: multithreaded callbacks (was Re: [AD] de fourium pointium ohium) |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: Allegro Developers List <conductors@xxxxxxxxxx>
- Subject: Re: multithreaded callbacks (was Re: [AD] de fourium pointium ohium)
- From: Stepan Roh <stepan@xxxxxxxxxx>
- Date: Sat, 14 Jul 2001 10:41:19 +0200 (CEST)
On Sat, 14 Jul 2001, Grzegorz Adam Hankiewicz wrote:
> On Fri, 13 Jul 2001, Peter Wang wrote:
> > Ok. The alternatives presented in that thread were:
> >
> > (0) pause the main thread when timer (etc.) callbacks are running
> >
> > (1) introduce a minimal synchronisation API for timers. Either:
> >
> > (a) the user is in charge of creating, locking, unlocking, and
> > destroying mutexes;
>
> I barely understand thread programming, but could 0 and 1a be mixed and
> chosen by the Allegro program? I mean, 0 could be the default, like some
> kind of aditional parameter of install_allegro, providing that default
> DOS-like compatibility everywhere, and if the program requests it, option
> 1a would be used.
This is certainly the best solution.
Have a nice day.
Stepan Roh