tmp/tmpc58i_r58/{from.md → to.md}
RENAMED
|
@@ -1,21 +1,21 @@
|
|
| 1 |
#### POSIX conformance <a id="fs.conform.9945">[[fs.conform.9945]]</a>
|
| 2 |
|
| 3 |
-
Some behavior is specified by reference to POSIX
|
| 4 |
such behavior is actually implemented is unspecified.
|
| 5 |
|
| 6 |
[*Note 1*: This constitutes an “as if” rule allowing implementations to
|
| 7 |
call native operating system or other APIs. — *end note*]
|
| 8 |
|
| 9 |
-
Implementations
|
| 10 |
-
|
| 11 |
-
|
| 12 |
-
POSIX behavior
|
| 13 |
-
|
| 14 |
-
systems
|
| 15 |
-
|
| 16 |
-
|
| 17 |
|
| 18 |
[*Note 2*: This allows users to rely on an exception being thrown or an
|
| 19 |
error code being set when an implementation cannot provide any
|
| 20 |
reasonable behavior. — *end note*]
|
| 21 |
|
|
|
|
| 1 |
#### POSIX conformance <a id="fs.conform.9945">[[fs.conform.9945]]</a>
|
| 2 |
|
| 3 |
+
Some behavior is specified by reference to POSIX [[fs.norm.ref]]. How
|
| 4 |
such behavior is actually implemented is unspecified.
|
| 5 |
|
| 6 |
[*Note 1*: This constitutes an “as if” rule allowing implementations to
|
| 7 |
call native operating system or other APIs. — *end note*]
|
| 8 |
|
| 9 |
+
Implementations should provide such behavior as it is defined by POSIX.
|
| 10 |
+
Implementations shall document any behavior that differs from the
|
| 11 |
+
behavior defined by POSIX. Implementations that do not support exact
|
| 12 |
+
POSIX behavior should provide behavior as close to POSIX behavior as is
|
| 13 |
+
reasonable given the limitations of actual operating systems and file
|
| 14 |
+
systems. If an implementation cannot provide any reasonable behavior,
|
| 15 |
+
the implementation shall report an error as specified in
|
| 16 |
+
[[fs.err.report]].
|
| 17 |
|
| 18 |
[*Note 2*: This allows users to rely on an exception being thrown or an
|
| 19 |
error code being set when an implementation cannot provide any
|
| 20 |
reasonable behavior. — *end note*]
|
| 21 |
|