On 5/11/06, Nicolas Cannasse <[EMAIL PROTECTED]> wrote:
Hi list,

I'm please to announce the release of Neko 1.3.
You can download it from here : http://nekovm.org/download
Changes are available here : http://nekovm.org/doc/changes/v1.3

Most of the changes are bug fixes and some API fixes or improvements.
One nice feature is the serialization of objects prototypes that can be
customized depending on your language needs :
see http://nekovm.org/doc/view/serialize

This is great news. Thanks for your continued efforts.

Can you give an example situation to explaing this:

"Serialization of bytecode function is possible, but will result in a
runtime exception when deserializing if the function offset in the
bytecode has changed."

ie what can make a function offset in the bytecode change?
Recompilation with extensive changes to the file (ie new functions
added)? Or is any change+recompilation likely to cause an offset
change?

Since I'm quite busy with haXe at the moment - which is relying on Neko,
I made a bugfix release and then the two promised features ( JIT and
Continuations ) will wait for 1.4 - probably around this summer.

Hmm, what kind of performance improvements do you expect with the JIT?
Can you hint at your design; how do you plan to implement the JITting?

Regards,

Robert Feldt

Enjoy !
Nicolas

--
Neko : One VM to run them all
(http://nekovm.org)


--
Neko : One VM to run them all
(http://nekovm.org)

Reply via email to