Archie Cobbs wrote:
Oliver Deakin wrote:
The word "pragmatic" springs to mind. FWIW, JamVM will print nothing
if no exception is pending. It didn't do this originally -- it blew
up with a SEGV. I changed it because a user reported an application
which didn't work with JamVM but it did with Suns VM (can't remember
which application, it was a long time ago).
This sounds right to me. As a user Id expect a call that prints
exception output to the screen to just print nothing and return if
there is no pending exception.
It's all very well bombing out with an assertion failure, but to the
average end-user it's still the VMs fault, especially if it works with
other runtimes (i.e. Suns).
Exactly - isn't this one of those differences to undocumented RI
behaviour that we should try to match?
There is nothing "undocumented" about this. The JNI spec says (though
not very clearly) that you should not call this function unless you know
there is a pending exception.
What I mean to say is that the behaviour when the function is called
without a pending exception is unspecified, and in that case I think it
makes most sense to match the RI.
However, that's not to say that we shouldn't be pragmatic, though, and
try to handle the situation gracefully.
-Archie
__________________________________________________________________________
Archie Cobbs * CTO, Awarix *
http://www.awarix.com
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Oliver Deakin
IBM United Kingdom Limited
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
