C++ and Beyond 2012: Andrei Alexandrescu - Systematic Error Handling in C++ | Going Deep

EDN Admin

Well-known member
Joined
Aug 7, 2010
Messages
12,794
Location
In the Machine
<p align="justify http://www.erdani.org/" target="_blank Andrei Alexandrescu presents "Systematic Error Handling in C++". This was filmed at http://cppandbeyond.com/" target="_blank C++ and Beyond 2012 <p align="justify Abstract: <p align="justify Writing code that is resilient upon errors (API failures, exceptions, invalid memory access, and more) has always been a pain point in all languages. This being still largely an unsolved (and actually rather loosely-defined) problem, C++11 makes no claim of having solved it. However, C++11 is a more expressive language, and as always more expressive features can be put to good use toward devising better error-safe idioms and libraries. <p align="justify This talk is a thorough visit through error resilience and how to achieve it in C++11. After a working definition, we go through a number of approaches and techniques, starting from the simplest and going all the way to file systems, storage with different performance and error profiles (think HDD vs. RAID vs. Flash vs. NAS), and more. As always, scaling up from in-process to inter-process to cross-machine to cross-datacenter entails different notions of correctness and resilience and different ways of achieving such. <p align="justify To quote a classic, "one more thing"! An old acquaintance—<a title="ScopeGuard http://www.drdobbs.com/article/print?articleId=184403758&siteSectionName=cpp ScopeGuard —will be present, with the note that ScopeGuard11 is much better (and much faster) than its former self.

Tune in. Learn. Thanks to Andrei, Herb and Scott for inviting C9 to film these wonderful sessions, rife with practical technical information for modern, professional C++ developers. <img src="http://m.webtrends.com/dcs1wotjh10000w0irc493s0e_6x1g/njs.gif?dcssip=channel9.msdn.com&dcsuri=http://channel9.msdn.com/Feeds/RSS&WT.dl=0&WT.entryid=Entry:RSSView:8f9989dded554bd8b5c5a0b301605cbd

View the full article
 
Back
Top