Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <4433EDB0.90508@sablevm.org>
Date: Wed, 05 Apr 2006 12:17:52 -0400
From: Etienne Gagnon <egagnon@sablevm.org>
User-Agent: Debian Thunderbird 1.0.2 (X11/20051010)
MIME-Version: 1.0
To: harmony-dev@incubator.apache.org
Subject: Re: [vmi] JNI spec interpretation?
References: <4432C57D.6070304@sablevm.org>
 <4432FA23.6080108@dellroad.org>	 <443385B0.8090506@gmail.com>
 <4433ADEE.5050700@sablevm.org>	 <4433D0FE.8020905@gmail.com>
 <4433D29F.1020400@dellroad.org>
 <d58509a80604050738l7c9f6df8s61bd9d143ccc8553@mail.gmail.com>
 <4433E2BA.6070300@googlemail.com> <4433E489.3000705@dellroad.org>
 <4433E5E2.1030005@googlemail.com>
In-Reply-To: <4433E5E2.1030005@googlemail.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enigE113B489541CD43A4264B4CC"

--------------enigE113B489541CD43A4264B4CC
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Oliver Deakin wrote:
> 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.


Let's say that I disagree to *impose* matching the RI's behavior for
undefined JNI code on Harmony VMs.  In many cases, matching the RI's
behavior on undefined JNI would require reverse engineering way beyond a
point I feel comfortable with.  I definitely think that Harmony's native
code should NEVER rely on undefined JNI behavior.  JIRA reports should
be raised for faulty JNI code.

On the other hand, I think that it would be a nice thing to keep an
explicit list of "expected" behavior for some widely used (by 3rd
parties) "undefined JNI", so that VM implementors are *encouraged* (not
*forced*) to provide such workarounds.  Some workarounds can be
expensive to implement; we had we had to implement a more expensive
approach for badly written JNI code that does not explicitly reserve
enough local native references (only 16 are guaranteed by default in the
spec).

So, I'll add a the ExceptionDecribe workaround to SableVM permanently,
but I do not wish feel obligated to do so. :-)

Etienne

-- 
Etienne M. Gagnon, Ph.D.            http://www.info2.uqam.ca/~egagnon/
SableVM:                                       http://www.sablevm.org/
SableCC:                                       http://www.sablecc.org/

--------------enigE113B489541CD43A4264B4CC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEM+2wjyrJi4rH84gRAq0EAJ9zYbo/6qEz9AC51mr/1YRAvk14DgCbBYG7
/qaXV71lKbcPwK+KVYqBFTQ=
=rNhi
-----END PGP SIGNATURE-----

--------------enigE113B489541CD43A4264B4CC--