On Wednesday 01 November 2006 21:49, Melchior FRANZ wrote: > * Durk Talsma -- Wednesday 01 November 2006 21:46: > > Yikes! That's not supposed to happen. You can safely comment out the > > exit(), as FlightGear has a fallback mechanism in case no route is found. > > That exit() *was* already commented out! (awynet.cxx:381) > It must have triggered another exit().
I the exit in question is in groundnetwork.cxx (around line 443, in my local copy. The awynet.cxx code isn't used yet. (FWIW, there's another exit() in groundnet around line 184. That one is to trap a potential internal programming error. Fortunately, this one has never triggered. Therefore, it looks like the safeguarding code can be deactivated) > > > Sorry for the aborted Flight... > > I'm over it. But I admit that I was quite p*ssed at first. :-} > > m. > Yes, my latest commit was bit rough. I;m sorry about that, but at the time I felt it was important to prioritize fixing a rather bad memory issue. A lot of other stuff has slipped in, which in retrospect wasn't quite ready yet. This not only includes the exits, but also the cerr messages you refer to in your other post, as well as some ground distance checking code, which in my own words can best be described as "a mess". I'll do a cleanup round after FSWeekend, and will commit a --hopefully-- much improved patch. Cheers, Durk ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
