サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
ノーベル賞
blog.think-async.com
As most Asio users will no doubt be aware, multiple threads can call io_service::run() to set up a pool of threads from which the completion handlers will be executed. This can be used in conjunction with io_service::post() to execute arbitrary tasks in the thread pool. In some rare spare moments I have used this facility to dabble in parallel algorithms (mainly to do with sorting large data sets)
[ part 1, part 2, part 3, part 4 ] Creating your own error conditionsUser-extensibility in the <system_error> facility is not limited to error codes: error_condition permits the same customisation. Why create custom error conditions?To answer this question, let's revisit the distinction between error_code and error_condition: class error_code - represents a specific error value returned by an oper
In the previous two posts, I showed some nifty macros for doing clean and simple stackless coroutines with asio. Hold on to your hats, because in this post we'll see what these coroutines can really do for your asio programs. A design goal of asio is to provide a basis for further levels of abstraction. One of the ways to develop abstractions on top of asio is to create what I like to call compose
このページを最初にブックマークしてみませんか?
『Thinking Asynchronously in C++』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く