[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Classpath build process and VM-specific issues
From: |
Andrew Haley |
Subject: |
RE: Classpath build process and VM-specific issues |
Date: |
Mon, 29 Mar 2004 10:30:13 +0100 |
Jeroen Frijters writes:
> Etienne Gagnon wrote:
> > Mark Wielaard wrote:
> > > I would like the vmdata field type then to be VMClass not Object.
> >
> > I disagree, as it imposes a restriction on what vmData actually
> > is. The most obvious implementation of vmData is to be a byte[]
> > instance holding the byte of a native pointer to an internal VM
> > non-moveable data structure.
>
> I'm glad to see we agree (although I don't think it's at all obvious
> that it should be a byte[], not all VMs use native code).
Eeeh. I can't imagine that either. If there's a strong argument for
holding native pointer in a byte[] ?
Andrew.
- RE: Classpath build process and VM-specific issues, (continued)
- RE: Classpath build process and VM-specific issues, Jeroen Frijters, 2004/03/25
- Re: Classpath build process and VM-specific issues, Robert Lougher, 2004/03/26
- RE: Classpath build process and VM-specific issues, Jeroen Frijters, 2004/03/28
- RE: Classpath build process and VM-specific issues, Jeroen Frijters, 2004/03/28
- RE: Classpath build process and VM-specific issues, Jeroen Frijters, 2004/03/28
Re: Classpath build process and VM-specific issues, Robert Lougher, 2004/03/29
Re: Classpath build process and VM-specific issues, Robert Lougher, 2004/03/29