Andy Ross wrote:
> I wrote:
> > This is the YASim XML parser. You hit this line when an
> > unrecognized tag is found in the XML file.
>
> In an attempt to keep blood pressures in a healthy range ...
Good. Hate to loose a contributor to cerebral hemorrhage. Very messy. Not
fun. ;-)
>
> It's still no more useful, IMHO. ...
The fact that the program exits gracefully as opposed to crashing with a
null de-reference helps considerably. The former says something
unacceptable or unhandled occurred. In this case, if we could turn on a
parser log it could do a lot in pinpointing XML problems.
Crashing, especially from de-referencing null pointers is usually
associated with bad code. Some systems used to do core dumps when null
pointers were de-referenced. Others drop out of the debugging environment.
Regardless of what happens, the event is not usually associated with
proper code operation and can miss lead efforts at debugging. If the code
gets to where it shouldn't, at least some attempt should be made to
indicated where, if not why.
Should we add good exception handling in the future, then throwing and
catching exceptions would make for a more robust way of dealing with a lot
of problems. And, it would probably be more informative.
Regards, and in near total ignorance of the parser and the problems that
suggested your stimulating solution,
Charlie H.
--
"There are two major products that come out
of Berkeley: LSD and UNIX. We don't believe
this to be a coincidence."
- J. Anderson
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
