Curtis L. Olson wrote: > Threading is *really* scarey in a program of this magnitude. > > I'd be adverse to adding additional threading especially if it > involves something like the property manager. > > There might be specific isolated instances where we can do it > reliably, but there is way too much that can bite us if we try to do > much threading.
Amen. The only purpose to doing threading in a C/C++ environment is SMP scalability (in Java, you have to use them for I/O multiplexing too; I consider this a bug, but at least there you have language syntax for the synchronization primitives). The property system is not likely, ever, to be a performance limitation requireing parallelization. There's nothing wrong with spawning a worker thread to do texture generation for a tile, or FDM computations, or whatnot. But glue them all together in the main loop. Andy -- Andrew J. Ross NextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com "Men go crazy in conflagrations. They only get better one by one." - Sting (misquoted) _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
