[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: TechRepublic article about languages to avoid in 2018
- From: Dibyendu Majumdar <mobile@...>
- Date: Thu, 8 Mar 2018 20:14:58 +0000
On 7 March 2018 at 21:35, Roberto Ierusalimschy <roberto@inf.puc-rio.br> wrote:
>> hey, the FFI is the nicest thing of LuaJIT! in fact, it happens to me
>> a lot that i start a project in a somewhat modern Lua, and then
>> appears something that would some C... at that point I have to
>> consider: is this a "serious thing, where i do care about the users?"
>> then I use the Lua C API. if it's a quick and dirty thing, then i
>> switch to LuaJIT and use the FFI. (no, i don't consider luaffi)
>
> luaffi is not a serious option, and cannot be; the whole philosophy of
> FFI demands a compiler. FFI is what made LuaJIT definitively a fork of
> Lua.
>
Did you mean that luaffi is not a serious option for inclusion in Lua
(because it is not ANSI C etc.)?
LuaJIT's ffi is a library and I am not sure why the inclusion of a
library should cause LuaJIT to be classed as a 'fork' - although
'fork' is problematic word in my view anyway.
luaffi is a valid attempt to provide the same library for Lua.
Regards
Dibyendu