You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
luajit is much faster at FFI calls than marshaling types into and out of a C API call. As long as all the C API bindings we have at the moment are sufficiently minimal, we can certainly provide luajit FFI equivalents that the Lua wrapper functions will still work with.
I don't know that it's worth also providing an Alien FFI binding, unless the syntax is similar enough to luajit FFI that it's possible to generate one from the other or otherwise automate the process of keeping them all in sync. ISTR there is a luajit FFI compatible FFI library for Lua 5.1/5.2 though, which would be a better option.
With a full set of FFI bindings, we could drop the Lua C API bindings entirely, and make luaposix into a pure Lua module!
The text was updated successfully, but these errors were encountered:
I'm not sure there is such a thing. I've been following the SUSv3 specifications for posix from the open group. You can reach the relevant pages from the most recent luaposix html documentation, or a bit of search engine archaeology - although it takes a little patience to navigate to the free online specs from the top of their website.
Thanks for the tips. I'll look at SUSv3 and try to sort out how all
these standards overlap and what to pick from each one (I'm only
interested the parts that work on Mac & Linux right now).
I'm not sure there is such a thing. I've been following the SUSv3
specifications for posix fro. The open group. You can reach the relevant
pages from the most recent luaposix html documentation, or a bit of
searching engine archaeology - although it takes a little patience to
navigate to the free online specs from the top of their website.
Reply to this email directly or view it on GitHub: #177 (comment)
luajit is much faster at FFI calls than marshaling types into and out of a C API call. As long as all the C API bindings we have at the moment are sufficiently minimal, we can certainly provide luajit FFI equivalents that the Lua wrapper functions will still work with.
I don't know that it's worth also providing an Alien FFI binding, unless the syntax is similar enough to luajit FFI that it's possible to generate one from the other or otherwise automate the process of keeping them all in sync. ISTR there is a luajit FFI compatible FFI library for Lua 5.1/5.2 though, which would be a better option.
With a full set of FFI bindings, we could drop the Lua C API bindings entirely, and make luaposix into a pure Lua module!
The text was updated successfully, but these errors were encountered: