Re: Classpath build process and VM-specific issues

[Etienne Gagnon]

Just to be cristal clear:

I propose to declare vmData of type Object, so that a native implementation
can choose to creat an instance of *any* type to hold the VM-specific value.

Etienne

Etienne Gagnon wrote:
> Etienne Gagnon wrote:
>
> > 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
>
>               ^^^^
>               bytes  (of course)
>
> Why byte[]?  For transparent protability to 16, 32, 64, 128, etc. bit
> processors without having to change anything.
>
> Etienne


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