Let's clear things up a bit (I hope):

1.  I'm not planning rushing the code into CVS since I know the XML
reader code is one of the most important areas of FlightGear. Get it 
wrong there and all sorts of pesky problems can arise.

2. The Expat code (along with EasyXML code) will remain available and 
will be used as a back up for XML documents my read can't handle. 
Meclhior already pointed to different encodings for example.

3. The only code modified to use the new xml reader is in 
props_io.[ch]xx and existing function calls are renamed rather than removed.

4. The main reason I put time into it is to try get rid of the 
occasional hicks I see when new terrain (along with new models) get 
loaded at runtime. I was hoping that a faster XML parser might improve that.

5. Expat (due to it's callback mechanism) can be made thread safe if 
you're cautious. The new code is full thread safe.

Erik

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to