Re: [Sablevm-developer] On the 1.1.1 release and further

[Etienne G. <gag...@uq...>]

Grzegorz B. Prokopski wrote:
> Another thing is SableJIT release. It's up to David when it happens,
> but I think we shouldn't wait too long with releasing this code as a
> _development_ release. We can even do it along 1.1.1, why not? I think
> that this way David (and we all) could get some bugreports from the
> users or/and gain confidence that SableJIT is actually usable in
> the real, wild world ;-) And for some people word "JIT" is magical...

I do not want to see SableJIT code under the /sablevm project tree before
the interface to the JIT is cleaned up and made into a minimal one,
instead of the "scattered all over the place" current status [unless I
am wrong and this has already been fixed].  I really want SableVM's source
code to remain as clean and easy to read/modify as possible.

I see SableJIT as an "add-on".  It's source code should reside mostly
(i.e. 99,9%) under the /sablejit project tree.  The additional 0.1% should
really be some very minimal changes in very few files (and very few places)
in SableVM's source code.

SableVM's inlined engine should remain the default interpreter engine, as
it is by far the most portable engine, and even sometimes the fastest
engine.  But, I am all in favor of making SableJIT an official add-on that
is released along SableVM, and set the build scripts so that a configure
option would actually generate a SableVM+SableJIT combination (but not by
default).

So, in the long term, I do not see the /sablejit tree disappearing.  I think
that SableJIT should remain distributed separately in sablejit-x.y.z.tar.gz
(where x.y.z matches sablevm's & sablevm-classpath's).

Etienne

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