Re: C++ religious war (was: llua Higher-level C API for Lua)
[
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: Coda Highland <chighland@...>
- Date: 2014年3月21日 17:33:05 -0700
On Fri, Mar 21, 2014 at 5:29 PM, William Ahern
<william@25thandclement.com> wrote:
> Imagine implementing (and debugging!) the same feature set within an IOCP
> framework. I'd sooner quit my job and work at McDonalds.
Qt does it by marshalling all the work onto a thread and then waiting
on the thread when you perform a blocking operation. It's possible,
and it's possible to do it with a clean user-facing API, but it's a
pain on the backend.
/s/ Adam
- References:
- 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), 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