On Sun, 10 Apr 2011 15:03:47 -0500, Curtis wrote in message 
<BANLkTi=4NOqL3gOuagCYkBV==9v504v...@mail.gmail.com>:

> Just for the record, I would be pretty strongly opposed to adding a
> thread for no particular benefit.  In fact I think the threshold of
> gained benefit needs to be pretty high to add another thread to the
> code.  Threads might seem simple at first, but they can hide nasty
> bugs that are almost impossible to find.  And even if the person
> submitting the code has validated everything and it's perfect --
> inevitably, someone will come and make changes somewhere in the code
> that affect the thread in some subtle way and we are back to having
> almost impossible to find bugs.  That doesn't mean we can't make a
> big mess of non-threaded code too, but threads are 100 times easier
> to screw up without realizing it until weeks or months later ... and
> when there is a problem, the concurrency of threads can make it
> extremely difficult to isolate where the bug actually is.

..ok, I volunteer for this stylish crash-n-burn 
so we can get back to the drawing board. ;o) 


> Regards,
> 
> Curt.
> 
> 
> On Sun, Apr 10, 2011 at 2:15 PM, Anders Gidenstam wrote:

> > The small changes needed to add a separate GC thread are available
> > here: http://www.gidenstam.org/FlightGear/misc/test/sg-gc-2.diff
> > http://www.gidenstam.org/FlightGear/misc/test/fg-gc-1.diff

..how do I apply these 2 in my git tree?

-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.

------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to