2005/11/28, Vassilii Khachaturov <[EMAIL PROTECTED]>: > problems). For the other parts of the patch, it is still relevant. > I'm going to rework it later by eliminating the above redundancy when > I have time (probably this weekend). That I was afraid of. That the new patch is on the way. ;-)
> > If yes, how to test if it works well? > > Depends on what kind of testing you want to do. Either look at the > exceptions thrown and try to induce each one of them, or probably > just do the regular flying and see if it is still OK. Flying is OK. But I'm not sure where I have to look for exceptions. Into terminal? I didn't see anything before, neither after the patch was applied. > Also look at the code and see if you find something obviously stupid that > I've > overlooked. Please don't rely on me. I'm totally beginner programer. > linux/Pentium IV 32 bit. So we have the same platform. So I didn't catch the point of > Since you are running on a different platform than I do > (I have the errno there), I would like to ask you to run the exception > checking snippet in this thread and report the results, while I'm doing > the final testing of the shortened patch. Regards Ladislav. _______________________________________________ Flightgear-devel mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
