Etienne, It would be great to see SableVM fully embrace Harmony Class Libs. Excellent approach!
The original design goal for kernel_path, the port of Harmony Class Libs to JCHEVM/SableVM, was to make absolutely minimal changes to the JVM. By design, this port uses little, if any, of the Harmony Class Libs VMI. In any case, feel free to borrow parts of kernel_path that make sense. Also, feel free to ask questions about it. For background on the top-level design descisions on kernel_path see: http://mail-archives.apache.org/mod_mbox/incubator-harmony-dev/200602.mbox/[EMAIL PROTECTED] On 3/25/06, Etienne Gagnon <[EMAIL PROTECTED]> wrote: > Archie Cobbs wrote: > > That makes sense.. i.e., if you want to make it into something of a > > research project to define the best possible Java/VM API then I'd be > > interested in that as well. Of course this will take more work. > > I think not. Internally, SableVM has a pretty modular stucture. All > we've traditionally done was to add some hook code for Classpath, not > the other way around. In other words, SableVM has never been designed > around Classpath's VMI (which actually was a moving target when I > started developing SableVM). So, since we can't use Classpath's code, > then I don't see how it would really help to closely stick to a > Classpath design. Maybe I will end up with an identical design, yet, my > feeling is that many little things might be different in the new solution. > > > First > > of course is defining what the goals and priorities are (if your goal > > were to do it quickly, then re-using the existing Classpath API would > > be the best option imho). > > It has always been the philosophy of SableVM project to take the time to > design and implement things as best as we could, instead of taking the > fastest shortcut. I know, many are anxious to see everything working > together "yesterday". If anoyone wants to do that, please feel free to > contribute the code that does it. Personally, I would much like to see > a well defined and correctly implemented VMI, that correctly takes care > of tricky class loading cases, etc. > Etienne > > -- > Etienne M. Gagnon, Ph.D. http://www.info2.uqam.ca/~egagnon/ > SableVM: http://www.sablevm.org/ > SableCC: http://www.sablecc.org/ > -- Weldon Washburn Intel Middleware Products Division
