Consider Keeping the Socket and LFS Libraries for CoronaCards?

[mlcraig]

From the docs, I see that support for several Corona modules has been removed.  These make good sense, but I’m wondering if you guys would consider keeping the socket and filesystem modules?

My motivation is to make card widgets that process some config data passed-in from Objective-C (eg: list of url’s or cached file paths).  These libraries would nice for making the component more autonomous.

Perhaps these are removed for security concerns with the advertisement model, but wanted to check with you guys.

Great work, thanks!

Mark

[walter]

Hi Mark, there were multiple considerations (security, code size, portability to platforms besides iOS/Android, etc). The great thing is that you can actually link these in yourself!

Both lfs and luasocket are standard Lua modules, so you can bring whatever version you want. There’s a dynamic symbol loader (dlsym) that looks for Lua modules based on the Lua module loader naming convention — lfs and luasocket should handle it.

Just make sure the linker doesn’t strip the symbols out (usually via special linker flags).

Oh, and luasocket might be a little more work b/c half of it is C code and the other half is Lua.

[walter]

Hi Mark, there were multiple considerations (security, code size, portability to platforms besides iOS/Android, etc). The great thing is that you can actually link these in yourself!

Both lfs and luasocket are standard Lua modules, so you can bring whatever version you want. There’s a dynamic symbol loader (dlsym) that looks for Lua modules based on the Lua module loader naming convention — lfs and luasocket should handle it.

Just make sure the linker doesn’t strip the symbols out (usually via special linker flags).

Oh, and luasocket might be a little more work b/c half of it is C code and the other half is Lua.