lua-users home
lua-l archive

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


On Sun, 19 Jan 2020 at 01:37, Sean Conner <sean@conman.org> wrote:
>   I generally write my own library code.  lposix (or is it luaposix?  I
> forget which one is the current standard) was just too large for my tastes,
> with functionality overlapping that of luasocket.  luasocket doesn't have a
> good design (in my opinion).  luafilesystem is too heavy to use (because of
> portability issues) and the list goes on.  My approach was to have well
> targetted libraries that work well together (and prevent unneccessary
> overlap), and I have:
>
>         org.conman.fsys         - file system related calls
>         org.conman.clock        - get time, set time, sleep
>         org.conman.process      - process creation
>         org.conman.signal       - signal related functions
>         org.conman.net          - sockets and network addresses
>         org.conman.tls          - TLS wrapper based on LibreSSL
>         org.conman.net.tcp      - create file system like IO over TCP
>         org.conman.net.tls      - create file system like IO over TLS
>         org.conman.nfl          - network event driver framework
>         org.conman.nfl.tcp      - handle TCP connections per coroutine
>         org.conman.nfl.tls      - handle TLS connections per coroutine
>         org.conman.pollset      - select()/poll()/kqueue()/epoll()
>         org.conman.syslog       - wrapper for syslog
>         org.conman.errno        - list of system error values
>         org.conman.env          - load environment vars into table
>
>   Theer are more, but I think you get the idea.  It took several years go
> get this all written and designed, and I'm still mucking with them to this
> day.

Nice. But I guess these are Linux only?

Regards
Dibyendu