On Monday 23 January 2006 12:50, Jon S. Berndt wrote: > As the number of XML files of various kinds (aircraft, engine models, etc.) > starts to grow, I'm beginning to think that some kind of run-time > validation of the input files could be very helpful. It's hard to catch all > kinds of possible errors that might be made in a configuration file - > whether it be in layout of the XML file, or content type, or out-of-limits > data. Often, these kinds of errors result in either bad operation, or > segfaults. That's not good for anyone.
IMO, decent runtime validation of XML config files would be a huge improvement. At the moment I use xmllint (one of the many handy tips picked up from #flightgear) which is great for picking up the more obvious errors. However, a validator with some knowledge of the expected content of tags and possibly values would be very nice indeed and could save quite a bit of time hunting around for the source of errors. Such a tool should not be set to run by default of course (fgfs startup is slow enough as it is) but would be an invaluable addition as a debug option. Cheers, AJ ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
