tmp/tmp4dtpc2bx/{from.md → to.md}
RENAMED
|
@@ -1,25 +1,25 @@
|
|
| 1 |
### Exceptions <a id="thread.req.exception">[[thread.req.exception]]</a>
|
| 2 |
|
| 3 |
Some functions described in this Clause are specified to throw
|
| 4 |
-
exceptions of type `system_error`
|
| 5 |
-
|
| 6 |
-
|
| 7 |
-
|
| 8 |
-
|
| 9 |
-
|
| 10 |
|
| 11 |
[*Example 1*: Consider a function in this clause that is specified to
|
| 12 |
throw exceptions of type `system_error` and specifies error conditions
|
| 13 |
that include `operation_not_permitted` for a thread that does not have
|
| 14 |
the privilege to perform the operation. Assume that, during the
|
| 15 |
execution of this function, an `errno` of `EPERM` is reported by a POSIX
|
| 16 |
API call used by the implementation. Since POSIX specifies an `errno` of
|
| 17 |
`EPERM` when “the caller does not have the privilege to perform the
|
| 18 |
operation”, the implementation maps `EPERM` to an `error_condition` of
|
| 19 |
-
`operation_not_permitted`
|
| 20 |
`system_error` is thrown. — *end example*]
|
| 21 |
|
| 22 |
The `error_code` reported by such an exception’s `code()` member
|
| 23 |
-
function
|
| 24 |
function’s error condition element.
|
| 25 |
|
|
|
|
| 1 |
### Exceptions <a id="thread.req.exception">[[thread.req.exception]]</a>
|
| 2 |
|
| 3 |
Some functions described in this Clause are specified to throw
|
| 4 |
+
exceptions of type `system_error` [[syserr.syserr]]. Such exceptions are
|
| 5 |
+
thrown if any of the function’s error conditions is detected or a call
|
| 6 |
+
to an operating system or other underlying API results in an error that
|
| 7 |
+
prevents the library function from meeting its specifications. Failure
|
| 8 |
+
to allocate storage is reported as described in
|
| 9 |
+
[[res.on.exception.handling]].
|
| 10 |
|
| 11 |
[*Example 1*: Consider a function in this clause that is specified to
|
| 12 |
throw exceptions of type `system_error` and specifies error conditions
|
| 13 |
that include `operation_not_permitted` for a thread that does not have
|
| 14 |
the privilege to perform the operation. Assume that, during the
|
| 15 |
execution of this function, an `errno` of `EPERM` is reported by a POSIX
|
| 16 |
API call used by the implementation. Since POSIX specifies an `errno` of
|
| 17 |
`EPERM` when “the caller does not have the privilege to perform the
|
| 18 |
operation”, the implementation maps `EPERM` to an `error_condition` of
|
| 19 |
+
`operation_not_permitted` [[syserr]] and an exception of type
|
| 20 |
`system_error` is thrown. — *end example*]
|
| 21 |
|
| 22 |
The `error_code` reported by such an exception’s `code()` member
|
| 23 |
+
function compares equal to one of the conditions specified in the
|
| 24 |
function’s error condition element.
|
| 25 |
|