This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Rmi compilation to native code

From: Tom Tromey <tromey at redhat dot com>
To: John Leuner <jewel at pixie dot co dot za>
Cc: Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>, u_a1bargnesi at umassd dot edu, java at gcc dot gnu dot org
Date: 22 Feb 2002 08:42:11 -0700
Subject: Re: Rmi compilation to native code
References: <3C7589EF.6070601@umassd.edu> <3C7591C7.3030009@waitaki.otago.ac.nz> <20020222112957.O424@bapli>
Reply-to: tromey at redhat dot com

>>>>> "John" == John Leuner <jewel@pixie.co.za> writes:

John> What about functionality of serialization. Does it work? Is it
John> compatible with the other JDK's?

At one point Warren did a lot of work to make gcj's serialization
compatible with the JDK's.  However it is possible that this has been
broken in minor ways since then.  What we really need is a
serialization regression tester.  Then we can just reject patches that
break serialization.

As to RMI, as far as I know nobody has tried RMI in a gcj or even
Classpath context.  I imported the TVT code drop but I never tried it.

Tom

Follow-Ups:
- Re: Rmi compilation to native code
  - From: Mark Wielaard

References:
- Rmi compilation to native code
  - From: u_a1bargnesi
- Re: Rmi compilation to native code
  - From: Bryce McKinlay
- Re: Rmi compilation to native code
  - From: John Leuner

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]