lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]


> Indeed. Ironically, though, Lua's own library tree is not
> set up that have /src/lib for the library source,
> and /include for all headers, including library ones.

That's not true. Check the Lua src directory and you will find a myriad of
include files that are not in /include. It's the same with LuaSocket.

> It would be rather nice if a library as useful as LibSocket
> were laid out so that it could readily be built for both
> dynamic and static use, and could readily be dropped into the
> library source tree of the core Lua distro, just like LuaThread
> can.

LuaThread is the exception, not the rule. Most libraries are completely
independent of the Lua source and distribution layout. As such,
LuaSocket has it's own directory tree that should not be mixed with
anyone else's directory tree.

The ability to build things statically and dynamically is improving with
time due to the new packaging system. The next release will be closer to
"easy to compile". :)

> Seems a pity to have to leave a single header file in /src/lib
> (when all the others are in /include) just so it can be called
> "io.h". (I tend to agree that "io.h" *is* a bad name, albeit
> for inelegant historical reasons.)

I am suggesting the opposite. Leave all headers in the LuaSocket source
directory and move luasocket.h to wherever you want.