Martin Spott wrote: > Hans Ulrich Niedermann wrote: > >> recently one of my aircraft had invalid XML, and the parser duly threw >> an exception. Unfortunately, fgInitFDM() considered it appropriate to >> report the error as >> >> ,---- >> | FlightGear aborting >> `---- >> >> and actually aborting FlightGear instead of at least printing something >> potentially helpful like >> >> ,---- >> | Error reading default aircraft: not well-formed >> | at /path/to/data/Aircraft/AN-225/AN-225-set.xml, >> | line 11, column 1 >> `---- > > Indeed, such error reporting would be terribly nice, last but not least > at malformed/missing aircraft Model files.
And that is easy: Someone with CVS karma just needs to remove that unnecessary-slash-harmful try/catchall instruction which has been present in src/Main/fg_init.cxx (according to CVS) since curt committed it in version 1.1 in september 2002. The actual exception provides that nice error message which is then printed if it is not explicitly ignored :) OK, there may be platforms where an uncaught exception does not print a proper error message, but would a missing catchall/ignoreall do harm on those? ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
