What is the Neko way of doing things? Port the the
Java or C library to haXe or call the C library?
From a pure Neko point of view, wrap the C library with a high-level
Neko API and wrap the Neko API with an haXe class it the way things are
usually done.
Every other part of the system will be implemented in
haXe except for the visual rendering. Is it useful to
have a growing base of NekoVM libraries like HTML
Tidy? Would it be faster to port a C library or a
Java library? I'm comfortabl with either language.
It depends a lot of which tools/libs theses libraries are using, the
quality of the code and the API, the amount of code...
I would go for either :
a) port the Java library to haXe , this require more code to write but
might be pretty straightforward.
b) write a Neko wrapper for the C library, more tricky since you need to
deal with Garbage Collector issues. OTOH if the library needs a lot of
CPU to perform the task, it might result in faster code this way
I guess it depends on your tastes & needs.
Nicolas
--
Neko : One VM to run them all
(http://nekovm.org)
