Hi, As some of you may know I have been working hard the last few weeks to improve a seamingly not very important utility called xmlgrep in the FlightGear utilities directory.
The reason for this was that the way this code works differs from the expat xml reader that FlightGear has been using for years now in that 'my' code tries to minimize memory usage as much as possible (at the cost of a bit of CPU work). This is important because memory management is a very expensive task and the result of this might be a highly fragmented internal memory which makes memory management even more time consuming. So the idea is that this new code would (hopefully) improve FlightGears response time when reading xml files at runtime (and most probably at startup also). The way it is set up right now (locally) is that the existing XML reading code has been renamed to readPropertiesValidating() and the new code has replaced these functions. The downside of this code is that it is not 100% validating (so it might accept xml syntax errors where expat didn't) and it doesn't support DTD's. Now for the real question: While I don't think those disadvantages are such a big deal in the end (both can be checked by loading the corresponding xml files in any modern browser) but what do you all think, would it be a bad idea to ditch support for DTD's? 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
