At first I thought this might be a good idea as well but it requires that a lot of logic be duplicated in the export script and it complicates testing, documentation, and distribution of exported data. What I think would be better is to include a LUA module that on the user's request can unpack the binary data into LUA tables. This keeps things fast in the case that the binary data does not need to be consumed by LUA.
At first I thought this might be a good idea as well but it requires that a lot of logic be duplicated in the export script and it complicates testing, documentation, and distribution of exported data. What I think would be better is to include a LUA module that on the user's request can unpack the binary data into LUA tables. This keeps things fast in the case that the binary data does not need to be consumed by LUA.
I understand why you designed this as you did, but it'd be nice if we could have access to the numeric array data.
At first I thought this might be a good idea as well but it requires that a lot of logic be duplicated in the export script and it complicates testing, documentation, and distribution of exported data. What I think would be better is to include a LUA module that on the user's request can unpack the binary data into LUA tables. This keeps things fast in the case that the binary data does not need to be consumed by LUA.