I was just thinking out loud. I'm in no position to know much about
tests anyway (Did 15+ years of game development mostly, where
asserts() were prevalent and manual QA - for both tools & game).
So I was just thinking if there are some unknown bugs in luajit
(interpretter, jit, etc), maybe porting a system to lua might help
since that system might come with extensive tests what is expected for
given situations, and the code in lua does not follow it, crashes,
etc. But it's a long shot. Even sqlite with it's extensive testing
suite, still has bugs, but from my work with sqlite they seem to be
most of the time new features.
Or take some other relatively small project - like zlib, libpng, and
completely port it there, and then reuse their tests, even port their
asserts, or so.
Again this might help nothing about the system, but having luajit
tests is really important.
(Oh, the llvm, gcc compilers must have some good tests too, a lot of
these probably won't make sense for lua/luajit in general, but some
others would)
On Thu, Aug 20, 2015 at 6:13 PM, demetri <demetri.spanos@xxxxxxxxx> wrote:
Here is a crazy idea. If someone is to port a rather well established
project to lua [snip]
I think this would be a great addition to the test suite already in
preparation, but perhaps I have misunderstood you: as far as I can
tell this wouldn't involve any work on LuaJIT itself. To put it another
way, I don't see how doing this (valuable, I agree) project proves that
we can continue feature development on LuaJIT internals.
Do you mean, perhaps, working on some specific LuaJIT feature that
would, for example, help optimize code for such a port of (say) sqlite?
If so what features (from the issue tracker or otherwise) do you think
might be helpful in that regard?
Or if I've just misunderstood you entirely please feel free to
correct me :)
Cheers,
Demetri
