RE: [Ikvm-developers] Support for JDK 1.5 features
Brought to you by:
jfrijters
From: Jeroen F. <je...@su...> - 2005-06-29 06:39:33
|
Retroweaver isn't necessary, setting the IKVM_EXPERIMENTAL_JDK_5_0 environment variable gives essentially the same capabilities. For ikvmc this environment variable only needs to be set a compilation time. Regards, Jeroen=20 > -----Original Message----- > From: ikv...@li...=20 > [mailto:ikv...@li...] On=20 > Behalf Of Matt Munz > Sent: Tuesday, June 28, 2005 21:04 > To: tj...@la... > Cc: ikv...@li... > Subject: RE: [Ikvm-developers] Support for JDK 1.5 features >=20 > Terry and list, >=20 > =20 >=20 > Thanks. That was the "hack" that I mentioned, and I think=20 > that its coverage may be less than desirable. [1] What about=20 > extending IKVMC to handle the 1.5 spec? Has anybody looked=20 > at what would be involved to do that? >=20 > =20 >=20 > [1] from the retroweaver docs: >=20 > Why am I getting a NoSuchMethodException/Error or a=20 > NoSuchFieldException/Error? > Most likely, you're using a class that did exist prior to JDK=20 > 1.5, but a new method/field for that class that didn't exist=20 > prior to JDK 1.5. You can't use new JDK 1.5=20 > classes/methods/fields in an earlier JVM. You can turn on the=20 > -verifyref option on Retroweaver to receive warnings when you=20 > reference classes, fields, or methods that don't exist in the=20 > VM that you are targetting. >=20 > =20 >=20 > - Matt >=20 > =20 >=20 > ________________________________ >=20 > From: Terry Laurenzo [mailto:tla...@gm...]=20 > Sent: Tuesday, June 28, 2005 1:56 PM > To: Matt Munz > Cc: ikv...@li... > Subject: Re: [Ikvm-developers] Support for JDK 1.5 features >=20 > =20 >=20 > I haven't had direct experience with it, but it seems to me=20 > that if you are careful you could probably combine=20 > Retroweaver with ikvm to obtain the desired result. I'm not=20 > saying that it would be pretty, but I don't see why it wouldn't work. >=20 > Terry >=20 > On 6/28/05, Matt Munz <mm...@ap...> wrote: >=20 > IKVM Devs, >=20 > The email archives suggest that JDK 1.5 support may be far off. [1] > Classpath does have the generics branch, [2] but I suppose it is too > incomplete to use, ATM? Two questions: >=20 > 1) Let's say I have some code today that uses 1.5 features=20 > (generics). > What is my best route to making that code available to .Net > applications, today? [3] >=20 > 2) Assuming that this is more difficult than, say, IKVMC'ing > 1.4-compatible bytecode, when may I expect this state of affairs to=20 > change (for the better)? Any guess as to when preliminary 1.5 support > will be available? >=20 > As a follow-on to #2, what are the major obstacles that stand in the > way of 1.5-compatibility for IKVM, and how big are they? =20 > While, for the=20 > moment, the current level of 1.4-compatibility is sufficient for me, I > will almost certainly need to handle 1.5 code in the future... >=20 > [1] http://sourceforge.net/mailarchive/message.php?msg_id=3D10038246 > [2] > http://developer.classpath.org/mediation/ClasspathDecisionsPag > e#head-273=20 > 8e96cc64a3b429eb50e2b0ce8ae732b70b1f9 > [3] Any solutions are welcome. I've read about some hacks for > converting bytecode from 1.5 to 1.4. Based on your experience, what's > the best approach? >=20 > - Matt Munz=20 >=20 >=20 >=20 >=20 > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles,=20 > informative Webcasts and more! Get everything you need to get up to > speed, fast.=20 > http://ads.osdn.com/?ad_idt77&alloc_id492&opclick=20 > <http://ads.osdn.com/?ad_idt77&alloc_id%16492&opclick>=20 > _______________________________________________ > Ikvm-developers mailing list > Ikv...@li... > https://lists.sourceforge.net/lists/listinfo/ikvm-developers >=20 > =20 >=20 >=20 |