> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
>
> How will GNU Classpath get the system properties, what is defined as
> the variable 'properties' in java/lang/System.java at the moment?
>
We should determine VM-independent things via a static initializer. This
should be native, as most of the properties are platform-dependent. Some of
those things *must* be determined at runtime, and others must be done at
compile-time (i.e. there is no way to determine them except if you just know
it beforehand, like the path separator (: on Win, ; on Unix).
> Does there need to be a way to fill this in from the system type
> variables of autoconf, ie those defined after calling
> AC_CANONICAL_SYSTEM, such as: build, host, target, etc?
>
We should use the target machine and OS type to determine some of the
properties. Anything that can be determined dynamically, probably should
be.
> Oh, what about grabbing system property information from Japhar/Kaffe
> at runtime? I think what I'm asking is does it need to be hard-coded
> when Classpath is compiled or can it be initialized once at runtime or
> does the JVM need to be queried via JNI for every getProperties()-ish
> call?
>
The VM-dependent things we get by calling
gnu.vm.VirtualMachine.getSystemProperties(). We merge those properties with
the ones we determined ourselves. That is part of the gnu.vm change I'm
working on.
> Are there cases where native code in Classpath needs to know the
> endian-ness of the machine, the size of an int, char *, etc?
>
> Brian
None that I know of.
--John Keiser
