boost/leaf
2
0
Fork 0
mirror of https://github.com/boostorg/leaf.git synced 2026-01-19 04:22:08 +00:00
Code Issues Projects Releases Wiki Activity

updated whitepaper

Browse Source
This commit is contained in:
Emil Dotchevski
2019-09-01 23:50:11 -07:00
parent 4b59b675fd
commit f6583c7dcd
1 changed files with 1 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
doc/whitepaper.md
View File

@@ -245,10 +245,7 @@ The major drawback of this appoach is that the *failure flag* is not communicate
### 6.2. C++ Exceptions
In C++, the default mechanism for dealing with failures is exception handling. This fixes the two major drawbacks of the `errno`-style APIs (see above):
* The check for errors is not only generic but completely automated: *by default*, if a function fails, the error will be communicated to the caller. Literally, the programmer can't forget to check the *failure flag*.
* Exception objects are generated dynamically, as if each failure gets its own `errno` instance that can't be stale.
In C++, the default mechanism for dealing with failures is exception handling. In this case,the check for errors is not only generic but completely automated: *by default*, if a function fails, the error will be communicated to the caller. Literally, the programmer can't forget to check the *failure flag*.
The drawback of virtually all implementations is overhead, both in terms of space and speed. Below we'll analyze the reasons for this overhead, and point out ways to alleviate them in future ABIs.