i'm in the process of getting japhar to build on windows (the non-native libs already build, and i've got a japhar executable that gives the usage message), and running around adding PR_EXTERN/PR_IMPLEMENT in a rather ad-hoc fashion just to get things to link. this isn't good, IMO. so, i'm going to take some time and try to clean up the extern api to japhar (not the JNI, mind you.) the intention being you could embed japhar in your program and use either the JNI or the other, internal api. this is analogous to what kaffe has with its KNI. All the pieces are there in japhar, they just aren't named things that are too helpful :) in the interest of being namespace friendly, i was going to use HVM_ as the prefix for all the extern calls into the vm, with the next word giving a better idea of where the call lives and what it does. for instance: throw_Exception would become HVM_ExceptionThrow. find_class would become HVM_ClassFind. I'll also be going through and possibly removing things from the external api where it makes sense. fright now japhar exports pretty much everything, and it doesn't need to -- why would the external api need the api call to the object finalizer, for instance. thoughts about any of this? suggestions? xtoph
