lua-users home
lua-l archive

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

On Friday, March 21, 2014, William Ahern <> wrote:
On Fri, Mar 21, 2014 at 05:35:26PM -0700, Coroutines wrote:
> I agree largely with what you have said, I think IOCP/AIO leads to
> much complication.  In the interest of getting back to the C++
> religious war thingy -- I counter your non-composability argument with
> std::function, booyah!

With std::function and lambdas, you can create producer/consumer libraries
that approach the elegance and conciseness of Node.js. :P

I agree with some others on this thread: the sweet spot for me is with C and
Lua. And if you implement your libraries and modules carefully, they can
work equally well in projects using either Lua, C, or C++ as the core
language or event driver.

IOCP is what you have if you want to quickly wait on multiple socket or file handles. It may suck or blow, but it's the right choice on Windows.

Likewise, basic functionality achieved, extending llthreads to take advantage of Microsoft's concurrency library and Apple's Grand Central.

A library with one task can be designed to be first class in more places.