> This also brings up the recurring question regarding the use of a third-party > XML parser. For once, I'll have to side with keeping our own, since that > would allow us to change the config file over in phases rather that all at > once.
There are othe rreasons why I'd like to keep our own parser. For one thing, I am very AR about knowing how each piece of code works. I want (and need) to be comfortable with the code that goes into JSBSim. XML is *very* broad, but the portion of it we need to use is extremely limited. I am very hesitant to bloat JSBSim, to add external requirements, etc. One of the key aims of JSBSim since the start has been to allow its use by college students of aerospace engineering. I'd prefer to continue to use a minimal set of XML only to the extent we need it to read in config files. The goal of some kind of default mechanism is well thought out. I think with not too much effort we can modify FGConfigFile to work as we wish. I would like to move towards more well-formed XML, but want to be careful on where this goes. Jon _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
