Re: What needs to be done to finish merging java.io ?

[Mark Wielaard <mark at klomp dot org>]

Hi,

On Thu, 2002-10-03 at 20:15, Tom Tromey wrote:
> 
> I think there are 3 issues in java.io:
> 
> * The native code is structured differently -- Classpath and libgcj
>   made different decisions about where to put native code, how to
>   write FileDescriptor, some other things like this.
>   Someone who understands the issues (in particular the Windows port)
>   would need to look into this to decide what to do.

The way Classpath did this is wrong. As noted in the following email.

    On Thu, 2002-07-11 at 18:19, Jeroen Frijters wrote:
    > I discovered a more serious problem with the current file i/o
    > implementation and I rewrote FileDescriptor, FileInputStream,
    > FileOutputStream & RandomAccessFile. The original implementation
    > has a problem with "ownership" of the handle. Since it is
    > possible to get the FileDescriptor from a FileIn/OutputStream it
    > is possible to close a handle, yet still have a stream that
    > "owns" that handle, this is a big problem. I fixed this by moving
    > the ownership of the handle to FileDescriptor (and all the native
    > methods as well).
    
    This is also how libgcj has it setup. We still need to merge the
    java.io stuff with that code. See the status of the merge at:
    http://gcc.gnu.org/java/libgcj-classpath-compare.html. I will look
    at their and your stuff and try to merge it with the Classpath code
    soon.

Although that was back in July I have still not looked at it. So much
for my definition of soon... If someone want to do it, please be my
guest :) His stuff can be found at http://radio.weblogs.com/0109845/.
It is a Java like VM for .NET based on the GNU Classpath libraries.

Cheers,

Mark