tmp/tmpx7ji3yfw/{from.md → to.md}
RENAMED
|
@@ -1,10 +1,10 @@
|
|
| 1 |
-
#####
|
| 2 |
|
| 3 |
[*Note 1*:
|
| 4 |
|
| 5 |
-
The format conversions described in this
|
| 6 |
POSIX-based operating systems because on these systems:
|
| 7 |
|
| 8 |
- The generic format is acceptable as a native path.
|
| 9 |
- There is no need to distinguish between native format and generic
|
| 10 |
format in function arguments.
|
|
@@ -13,15 +13,15 @@ POSIX-based operating systems because on these systems:
|
|
| 13 |
|
| 14 |
— *end note*]
|
| 15 |
|
| 16 |
Several functions are defined to accept *detected-format* arguments,
|
| 17 |
which are character sequences. A detected-format argument represents a
|
| 18 |
-
path using either a pathname in the generic format
|
| 19 |
-
|
| 20 |
-
|
| 21 |
-
format
|
| 22 |
-
|
| 23 |
|
| 24 |
[*Note 2*: Some operating systems may have no unambiguous way to
|
| 25 |
distinguish between native format and generic format arguments. This is
|
| 26 |
by design as it simplifies use for operating systems that do not require
|
| 27 |
disambiguation. An implementation for an operating system where
|
|
@@ -40,12 +40,12 @@ native-to-generic and generic-to-native formats respectively. If
|
|
| 40 |
If the native format requires paths for regular files to be formatted
|
| 41 |
differently from paths for directories, the path shall be treated as a
|
| 42 |
directory path if its last element is a *directory-separator*, otherwise
|
| 43 |
it shall be treated as a path to a regular file.
|
| 44 |
|
| 45 |
-
[*Note 4*: A path stores a native format pathname
|
| 46 |
-
[[fs.path.native.obs]]
|
| 47 |
pathname, related as given below. The implementation may generate the
|
| 48 |
generic format pathname based on the native format pathname (and
|
| 49 |
possibly other information) when requested. — *end note*]
|
| 50 |
|
| 51 |
When a path is constructed from or is assigned a single representation
|
|
|
|
| 1 |
+
##### Argument format conversions <a id="fs.path.fmt.cvt">[[fs.path.fmt.cvt]]</a>
|
| 2 |
|
| 3 |
[*Note 1*:
|
| 4 |
|
| 5 |
+
The format conversions described in this subclause are not applied on
|
| 6 |
POSIX-based operating systems because on these systems:
|
| 7 |
|
| 8 |
- The generic format is acceptable as a native path.
|
| 9 |
- There is no need to distinguish between native format and generic
|
| 10 |
format in function arguments.
|
|
|
|
| 13 |
|
| 14 |
— *end note*]
|
| 15 |
|
| 16 |
Several functions are defined to accept *detected-format* arguments,
|
| 17 |
which are character sequences. A detected-format argument represents a
|
| 18 |
+
path using either a pathname in the generic format [[fs.path.generic]]
|
| 19 |
+
or a pathname in the native format [[fs.class.path]]. Such an argument
|
| 20 |
+
is taken to be in the generic format if and only if it matches the
|
| 21 |
+
generic format and is not acceptable to the operating system as a native
|
| 22 |
+
path.
|
| 23 |
|
| 24 |
[*Note 2*: Some operating systems may have no unambiguous way to
|
| 25 |
distinguish between native format and generic format arguments. This is
|
| 26 |
by design as it simplifies use for operating systems that do not require
|
| 27 |
disambiguation. An implementation for an operating system where
|
|
|
|
| 40 |
If the native format requires paths for regular files to be formatted
|
| 41 |
differently from paths for directories, the path shall be treated as a
|
| 42 |
directory path if its last element is a *directory-separator*, otherwise
|
| 43 |
it shall be treated as a path to a regular file.
|
| 44 |
|
| 45 |
+
[*Note 4*: A path stores a native format pathname
|
| 46 |
+
[[fs.path.native.obs]] and acts as if it also stores a generic format
|
| 47 |
pathname, related as given below. The implementation may generate the
|
| 48 |
generic format pathname based on the native format pathname (and
|
| 49 |
possibly other information) when requested. — *end note*]
|
| 50 |
|
| 51 |
When a path is constructed from or is assigned a single representation
|