tmp/tmpx939av_t/{from.md → to.md}
RENAMED
|
@@ -6,11 +6,11 @@ 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
|
| 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
|
|
|
|
| 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
|