Subject: Re: Commit: back out martin's changes ;-(
From: David Mandelin (mandelin@cs.wisc.edu)
Date: Wed Sep 05 2001 - 12:09:40 CDT
Patrick Lam wrote:
>
> On Wed, 5 Sep 2001, David Mandelin wrote:
>
> > SDL and wxWindows each have XP thread libs. In wxWindows, there are
> > 1200-1500 LOC per platform for threads, mutexen, and condition
> > variables.
>
> Hmm, that's a lot of code. I'm not familiar with their approach.
I just checked Python. It uses about 300-500 LOC per platform. I think
the size difference is mostly from formatting and style. Also, wxWindows
has made some effort to improve Posix condition variables.
> > I'm confused about the goal here. I don't see what's wrong with timers
> > and idle handlers. As long as they send everything through the event
> > queue, the program is effectively single-threaded, even if the system
> > uses multiple threads to make it happen. There shouldn't be any race
> > conditions.
>
> Dom asserts that the UT_Timer class now interrupts what's currently in
> progress. It's not a timer that executes from the event queue. So that
> is effectively multithreaded.
Yes, but the timers could be changed so that they don't call functions
directly, but post "timer" events instead. Similarly, the event loops
could be set up to generate "idle" events every time AbiWord goes idle.
The event mapper would take care of the rest.
This archive was generated by hypermail 2b25 : Wed Sep 05 2001 - 12:09:43 CDT