Some thoughts.... >Most people code Neko with haXe,
This is true for software, but prob not best for compiler / VM design. NekoML is probably the best bet, here. It'd produce much smaller, faster and efficient compilers. >zip and other formats > http://code.google.com/p/hxformat/ > >reflection > http://haxe.org/doc/cross/reflect > >tutorials on Neko using haxe ( including IO ) > http://haxe.org/doc/neko This is fine if you code in haXe. However, Justin has a point; the Std library points to the ndll functions that perform these tasks (though reflection isn't needed in the same way, as it's more flexible in Neko, so exclude that). Therefore, looking at the haXe Std library would be a good place to work out how Neko performs certain tasks. I will also point out that, when writing apps in haXe targeted at Neko, there is a switch you can use to output Neko source code. This is great for seeing how certain things are managed, such as haXe's namespaces, reflection and what have you, as haXe has just about every feature you can dream up ;-) Regards, Lee On 30 Sep 2011, at 23:39, johann Sorel wrote: > Hello, > > I don't really know where to start, so let's start be the context. > > I am a Java developer specialized in GIS (Geographic Information > System), stuffs like google maps, worldwind ... and so on ... > About two years ago the company behind Java (Sun) has been buyed by > Oracle and since then all the different implementation on JVM started > to dye. > - Apple stopped it's jvm and will rely on openJDK. > - IBM stopped contributing to apache harmony and moved on openjdk > - Google Davlik VM is in a lawsuit with Oracle > - Apache Harmany has be confirmed it will never be certified as a JVM > and so project is nearly dead > + all the ugly backstabs oracle did ... > > ... all this to say, after 6years of pleasant java programming, this > ecosystem has turned in a golden cage with a single VM (OpenJDK) > remaining and nearly completly under Oracle control. > > So before things get even worse I started exploring other solutions > and stopped my choice on ParrotVM to built my project : Eria, a > paradygm programming model and a static+constraint language > http://sourceforge.net/p/eria > > After several weeks I manage to achieve something starting to work, > but Parrot is painfull, full of perl-ish approaches, nearly inexistant > technical docs. It takes an incredible amount of time just to find out > how to do something and requiered to learn PIR and winxed to have a > reasonable programming language. > > And so (again) I started to search some more VMS, lighter ones. And > now I'm interested by Neko VM. > > If someone could answers my questions, I would greatly appreciate :) > - license : are there plans to change the license ? to something more > 'free', public domain or give the copyright to a foundation ? > it's not that I don't like the GPL license but I still have a very bad > experience with OpenSolaris which has suddenly change license to > something private (thanks oracle again). I guess you can understand I > have a few fears about GPL, it's not a full proof guarantee for the > futur. > - NekoVM : is there a basic IO support in nekoVM, at least to read and > write files ? so I could build a parser Eria -> Neko with it ? > - NekoVM : some archive support ? zip, tar, gz, anything ? > - NekoVM : my language requieres to have some advance reflexion, I > want to store constraint informations on a function arguments, x > between 0 and 10 . > - NekoVM : how are objects organize ? in parrot I could store > primitives/class/functions in namespaces and acces them using > reflexion. Is there something similar in NekoVM. something like paths > or namespaces ? > - any IRC channel somewhere for neko project ? > > > Thanks, > > johann Sorel > > ____________________________________________________________ > Publish your photos in seconds for FREE TRY IM TOOLPACK at > http://www.imtoolpack.com/default.aspx?rc=if4 > > > > -- > Neko : One VM to run them all > (http://nekovm.org) -- Neko : One VM to run them all (http://nekovm.org) -- Neko : One VM to run them all (http://nekovm.org)
