On Tue, Sep 27, 2011 at 03:02:28PM +0200, ext Robin Burchell wrote: > On Sat, Sep 24, 2011 at 11:48 PM, Иван Комиссаров <[email protected]> wrote: > > Second - if we provide new API, should it be synchronous (like QFile) or > > asynchronous (like Q*Socket)? > > My personal thoughts would be to drop the synchronous like a brick, > because if it exists, people who don't know any better *will* (ab)use > it because it's "easier" or simply because examples/other people do > and they don't know what that really means, and then you end up with > poorly-performing applications. > an incorrectly used async api (nested event loops, in particular) is a source of much harder to debug problems, so it's not as clear-cut at it may seem.
i wonder whether it would be possible to make a qthread subclass which would be a generic sync wrapper for async apis, so one could dispose of the waitFor*() in the i/o devices without requiring the users to write lots of boilerplate code. _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
