I vote in favor of enabling threads. I've ran FlightGear for ten hours, with
threads enabled, without any problems.
In addition, it's probably a good time to do this now, just after a release.
Because enabling threading now in cvs will give the developers ample time to
iron out any bugs well before the next release is coming up.
On Friday 16 April 2004 18:50, Andy Ross wrote:
> Durk Talsma wrote:
> > I experienced (some of) these pauses as well when I built FlightGear
> > without threading support (See my bug reports on fgfs-devel last week,
> > the "smoother performance" refers to the absence of the pauses
> > :-)). After enabling threading again, the pauses went away. So my
> > guess it that you are using an untreaded version of FlightGear.
> Which brings up a good question: what are the arguments against
> enabling threads by default? Obviously some platforms lack thread
> support, but those could turn it off automatically in the
> configuration script.
> It seems like many/most people are using threads without problems. So
> if we're still worried about bugs, the best way to find them would be
> to enable it globally.
> Flightgear-devel mailing list
> [EMAIL PROTECTED]
Flightgear-devel mailing list