It seems interesting that nekoVm is lightweight, embeddable and faster than many languages...
It would be appreciable if it's possible to add examples for making this language popular and easy to learn.
The َAutoIt or actionScript help files are good models.
The purpose (from this issue...) is to teach newbies and beginner users first , not the developers and/or advanced users
Regards,

See travis-ci/travis-ci#4583
Would you make the old urls work soonish as TravisCI haxe builds depend on them.

We could consider hosting the binaries for Neko using Github releases, the way we do it for Haxe too.
https://github.com/HaxeFoundation/neko/releases

https://nekovm.org/foundation/
produces a 404 error

When testing out TravisCI haxe support for OSX builds, I noticed that our haxe OSX binaries archive is 64bit. But the nekovm website only provides 32bit neko...
It has been a problem for quite some time.

The weird thing is, the haxe OSX installer does install a 64-bit neko... So why not put the 64-bit neko on the neko website? ;)

Here below is the 64-bit neko archive extracted from our official haxe mac installer:
https://dl.dropboxusercontent.com/u/2661116/neko-2.0.0-osx64.tar.gz

As title said, links to the Neko mailing list at http://nekovm.org/ml are all dead :(

Not sure why.
Asking Nicolas for help.

I'm trying to build the server.hxml but I get this error

I already runned haxe install server.hxml which should install it's dependencies?

So I thought maybe I only need to do ufront build ?

.. or only ufront server?

update:
After some investigation I found that the import statements aren't correct (fixed here #4). I now added this on all source files:

import ufront.*;
import ufront.web.*;
import ufront.api.*;

But then I get this error:

This means there is something in detox incorrect.. Now I'm stuck..

How do I get the thing working 😄 ?

All links on this page are dead:
http://nekovm.org/ml

@ncannasse what is the correct way to get subscribed nowadays?

Pretty much like haxe.org, there is no need to use ufront for this simple web site...
@ibilon Would you do the conversion just like you did for haxe.org?

Neko (the language) is, if I'm reading this correctly, meant to be used as a compiler target.
However, before actually being executed, it has to be run through nekoc (a NekoML program).
The output of nekoc is useful, as there is little room for error when interpreting it, or possibility for unimplemented feature ambiguity (like NXML).
Furthermore, there is always the case of people, for whatever reason, shipping ".n" binaries (such as the bootstrap binaries that come with the source of Neko - even assuming nekoc is useless for a VM, NekoML can export to the Neko intermediate form, so running it would be useful - but you can't run NekoML without NekoML or a way to execute the NekoML .n file...), so even a VM that starts from Neko is going to encounter issues.

The Virtual Machine docs don't actually describe the Virtual Machine. They describe the implementation of the Virtual Machine and how to communicate it, which is certainly useful, but doesn't actually give any way for prospective implementors to write an interpreter.
They instead have to go searching through the existing interpreter for the information (specific points of interest are module.c and interp.c), which is not ideal.

For these reasons (and presumably you can work out more), it would be nice to have documentation on the ".n" format, the bytecode compression and the actual instruction formats in the file.
(Another note: There is also no table, anywhere that I know, that directly puts numbers to the names of the opcodes. It's all implied by C enums.)