janko metelko a écrit :
Hi Nicolas,

I looked at the neko.net.Socket and various other modules. But isn't the situation there reverse from what I need?

I am really sorry if I am wrong. The way I understand these are libraries... The code wraps haxe functions around native functions that it loads with neko.Lib.load() .

First, you need to wrap your neko libraries to be usable from haXe. That's what neko.net.Socket is doing for instance.

Then, you can compile the haXe module as .n

The export table will contain a single entry called "classes", which contain the whole classes and packages that have been compiled by haXe.

You can then access to a given class for example by using :

$exports.my.package.MyClass

(or the equivalent by using Neko API)

You can create an instance by calling MyClass.new(p1,p2,...) and the call the methods etc.

Hope that helps,
Nicolas


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

Reply via email to