Implementing Harmony's VM Interface

Hi all,

So, the relicensing will be done shortly.  I first want to double check
all dependencies to make sure we don't hit any license compatibility.
(We shouldn't, but I prefer to have peace of mind).

Now, the next task is to adapt SableVM to work with the Harmony VM
Interface (VMI).  Thanks to IBM, this interface seems very well defined,
and quite elegant.

I think that SableVM could gain much in stability by dropping the
ill-defined Classpath interface, and by implementing Harmony's VMI.  As
a result, SableVM would strictly depend on Harmony's Kernel classes.

Classpath compatibility would not really be broken by such change.  I am
sure that SableVM could use a class library composed of:
- Harmony classes.
- Classpath classes for packages not yet implemented in Harmony.

So, here are links to the appropriate documentation:
http://svn.apache.org/viewcvs.cgi/*checkout*/incubator/harmony/enhanced/classlib/trunk/doc/vm_doc/html/index.html
 
http://svn.apache.org/viewcvs.cgi/*checkout*/incubator/harmony/enhanced/classlib/trunk/doc/vm_doc/html/group__VMInterface.html
http://svn.apache.org/viewcvs.cgi/*checkout*/incubator/harmony/enhanced/classlib/trunk/doc/kernel_doc/html/index.html


Have fun reading!

Etienne

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

signature.asc
Description: OpenPGP digital signature

_______________________________________________
SableVM-devel mailing list
SableVM-devel@xxxxxxxxxxx
http://sablevm.org/lists/control/listinfo/sablevm-devel