>> Well, Lua supports calling both ways. A call isn't a straight C call,
>> though (in Lua, it's a straight Lua function invocation), but a call
>> that follows a certain calling protocol. Going from Lua to pure C or
>> pure C to Lua requires a bit of glue code much like sqlite does for
>> its parameter bindings.
>> Am I right that if we were to run this experiment with the
>> move-tracking-2 branch code, that the entire client and library would
>> be subject to conversion to the higher level language?
> No! That would be literally years of rewriting and debugging and
> re-testing, not to mention interesting interfacing with the rest of the
> (pool-bound) code.
I assume we could start by writing one line of new code, getting it to
compile and run (that would involve a lot of configuration work and
learning, initially), and then extend bit by bit as desired. Probably
no point in ever rewriting the *whole* of anything, only new stuff and
anything that needs to be largely rewritten for another reason.
Received on 2015-03-13 15:41:40 CET