Understood -- my point is that "blowing up" and "corrupting internal data structures" is not something you would do by design.
So what does SableVM do if I call ExceptionDescribe() with no pending exception? I changed the launcher because I agree that JNI code shouldn't misbehave, but making SableVM tolerant is good too for those cases where the fix is not under our control etc. Regards, Tim Etienne Gagnon wrote: > By specification, the general contract for misbehavior of JNI code is > "undefined VM behavior", which can mean anything from "blow up" to > "corrupt internal data structures": > > 11.8.1 No Checking for Programming Errors > > The JNI functions do not check for programming errors. Passing illegal > arguments to JNI functions results in undefined behavior. [...] > > Etienne > > Tim Ellison wrote: >> So what should a VM do if somebody calls ExceptionDescribe() and there >> is no pending exception? > -- Tim Ellison ([EMAIL PROTECTED]) IBM Java technology centre, UK. --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
