Thinking Asynchronously in C++

Wednesday, April 14, 2010

System error support in C++0x - part 5

›
[ part 1 , part 2 , part 3 , part 4 ] Creating your own error conditions User-extensibility in the <system_error> facility is not li...
459 comments:
Monday, April 12, 2010

System error support in C++0x - part 4

›
[ part 1 , part 2 , part 3 ] Creating your own error codes As I stated in part 1 , one of the principles behind the <system_error> f...
197 comments:
Friday, April 09, 2010

System error support in C++0x - part 3

›
[ part 1 , part 2 ] Enumerators as class constants As we have seen, the <system_error> header defines enum class errc : enum class e...
59 comments:
Thursday, April 08, 2010

System error support in C++0x - part 2

›
[ part 1 ] error_code vs error_condition Of the 1000+ pages of C++0x draft, the casual reader is bound to notice one thing: error_code an...
162 comments:
Wednesday, April 07, 2010

System error support in C++0x - part 1

›
Among the many new library features in C++0x is a little header called <system_error> . It provides a selection of utilities for manag...
247 comments:
Tuesday, April 06, 2010

Bind illustrated

›
Asynchronous operations in Asio all expect a function object argument, the completion handler, which they invoke when the asynchronous opera...
208 comments:
Monday, April 05, 2010

Timeouts by analogy

›
Most networking-enabled applications have to deal with timeouts. Read or write operations may continue indefinitely, and programs need a way...
355 comments:
›
Home
View web version

About Me

chris
Author of the Boost.Asio library for networking in C++.
View my complete profile
Powered by Blogger.