Am 20.11.13 13:33, schrieb Lourival Vieira Neto: > On Wed, Nov 20, 2013 at 6:36 AM, Marc Balmer <[email protected]> wrote: >> Am 18.11.13 09:07, schrieb Marc Balmer: >>> Am 17.11.13 13:05, schrieb Marc Balmer: >>>> I came accross a small library for converting data to an from C structs >>>> for Lua, written by Roberto Ierusalimschy: >>>> >>>> http://www.inf.puc-rio.br/~roberto/struct/ >>>> >>>> I plan to import it and to make it available to both lua(1) and lua(4) >>>> as follows: >>>> >>>> The source code will be imported into >>>> ${NETBSDSRCDIR}/sys/external/mit/struct unaltered and then be modified >>>> to compile on NetBSD. >>>> >>>> Then ${NETBSDSRCDIR}/sys/module/luastruct/ and >>>> ${NETBSDSRCDIR}/lib/lua/struct/ directories will be added with the >>>> respective Makefiles etc. >>> >>> After discussion we lneto@ and others we realised that there are several >>> such libraries around, and that I as well as lneto@ wrote one. SO we >>> decided to merge our works and have a library that allows to >>> encode/decode structured binary data in one call (my work) and that >>> allows to access individual fields as well (lneto@'s work). >>> >>> Now we need a name that covers both uses cases. It could be "memory" >>> because it deals with memory, or just "data", which I favour. >>> >>> Opinions on the name? >> >> Since no one replied, it will go by the name 'data' and be available for >> "both" Luas. > > 'Data' is fine for me; I don't have a better suggestion anyway =). > >> @lneto: I will start with the pack/unpack parts, you can then add your >> stuff whenever you want, ok? > > Just fine for me. However, I think we need to define the API before > (re)starting coding.
Yes. I will meet Justin at LWS, discuss with him, and then mail out what we discussed, so you can chime in. ok?
