Here are few questions for you:
1) Are there any native methods for java.lang package ? They seem to be
missing from native/ directory. Or is it vm creators responsibility to
implement them all ?
2) What interfaces should vm implement to be classpath aware (except
JNI) ? I've heard something about VMI, but all functions already have
definitions - should they be overridden ?
3) Is there any way to easily replace parts of classpath with
vm-specific code ? I'm thinking mainly about native_state (current
implementation is state of art vm-independence, but some VMs may just
want to implement pointer to native data in obj data, and thus save a
lot of time to access them) and using native-native interface for
java.lang,java.lang.reflect and java.io instead of JNI.
4) Fields in java.lang.Class are not a good idea. This class has to be
treated specially by vm anyway, and there is a hell lot of native calls
- saving 5 of them is not a bonus, but it can cause some problems to vm
implementors; for example in chives we want to implement it as normal
object, with native data after obj fields, and current design will force
use to loose 12 bytes per class for nothing (as we would need to
duplicate this 3 fields (with maybe exception of signers) anyway)
5) What are these class signers, BTW ?
6) Is java.util package finished ? I could not find Vector class there.
Artur
