[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: C++ religious war (was: llua Higher-level C API for Lua)
- From: William Ahern <william@...>
- Date: Fri, 21 Mar 2014 19:11:56 -0700
On Fri, Mar 21, 2014 at 05:35:26PM -0700, Coroutines wrote:
<snip>
> 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.
- References:
- Re: C++ religious war (was: llua Higher-level C API for Lua), Hisham
- Re: C++ religious war (was: llua Higher-level C API for Lua), steve donovan
- Re: C++ religious war (was: llua Higher-level C API for Lua), Roberto Ierusalimschy
- Re: C++ religious war (was: llua Higher-level C API for Lua), Jeremy Ong
- Re: C++ religious war (was: llua Higher-level C API for Lua), steve donovan
- Re: C++ religious war (was: llua Higher-level C API for Lua), Andrew Starks
- Re: C++ religious war (was: llua Higher-level C API for Lua), Sean Conner
- Re: C++ religious war (was: llua Higher-level C API for Lua), Coroutines
- Re: C++ religious war (was: llua Higher-level C API for Lua), William Ahern
- Re: C++ religious war (was: llua Higher-level C API for Lua), Coroutines