[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Classpath build process and VM-specific issues
From: |
Jeroen Frijters |
Subject: |
RE: Classpath build process and VM-specific issues |
Date: |
Fri, 9 Apr 2004 10:35:50 +0200 |
Steven Augart wrote:
> If we were to do this in the GNU Classpath Java code, then the only
> solution I see is to use a preprocessor, and expand gpointer
> to an int or long as appropriate, based upon the standard pointer
> representation in that platform's usual ABI.
That wouldn't work for me. My (single) binary runs on both 32 and 64 bit
platforms. That's why I like using an object reference. BTW, I don't
actually store a native pointer in an object reference. I replace
RawData references with a native pointer type that the CLI support
(System.IntPtr). This is a primitive type, but it can also be boxed when
you assign it to an object reference.
Regards,
Jeroen
RE: Classpath build process and VM-specific issues, Jeroen Frijters, 2004/04/09
RE: Classpath build process and VM-specific issues, Jeroen Frijters, 2004/04/09
RE: Classpath build process and VM-specific issues,
Jeroen Frijters <=
RE: Classpath build process and VM-specific issues, Jeroen Frijters, 2004/04/09
RE: Classpath build process and VM-specific issues, Jeroen Frijters, 2004/04/09