@nicolas: tests and documentation don't have to exclude each other - no? Maybe we have to differentate between tests for the libraries and tests for neko (and also haxe) runtime and compiler.
when I asked for tests for the libraries I simply wanted to "feel" how the they work. Maybe tests make it easier to not just to understand it theoretically. Tests for the neko vm and the compiler are another story in terms of effort (for you) I guess. But what do you think - could this be a long term task? @vitaly/nicolas: vitaly already made a unittest library for neko: UnitNeko on insideable.com. Maybe it would make sense to have also a 'projects' site on nekovm.org. I think http://lib.haxe.org/ is not really the appropretiate place because it is really an exclusive neko thing. 2007/11/29, Nicolas Cannasse <[EMAIL PROTECTED]>: > Vitali Falileev a écrit : > > > > > > 2007/11/29, Nicolas Cannasse <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>>: > > > > > > The reason is simple : I didn't use unit testing while developping Neko. > > I did a lot of tests of course but I didn't put them together in some > > source files. > > > > You might want to contribute your own tests, that would be helpful but > > needs to cover all the aspects of the language. > > > > > > Nicolas, it is not easy to cover *your code* with tests because only you > > keep in mind the idea how NekoVM works ;-) Can we ask you to find a time > > to make at least few tests? It will be very helpful for NekoVM community. > > Well, I think there's already a good language reference explaining how > things are supposed to work - and as long as I know they do :) - as well > as complete documentation for all standard libraries functions. I'm not > sure then if it's some work that can be done only by myself ;) > > Best, > Nicolas > > -- > Neko : One VM to run them all > (http://nekovm.org) > -- Neko : One VM to run them all (http://nekovm.org)
