tmp/tmpw21jct_w/{from.md → to.md}
RENAMED
|
@@ -21,11 +21,11 @@ path using either a pathname in the generic format [[fs.path.generic]]
|
|
| 21 |
or a pathname in the native format [[fs.class.path]]. Such an argument
|
| 22 |
is taken to be in the generic format if and only if it matches the
|
| 23 |
generic format and is not acceptable to the operating system as a native
|
| 24 |
path.
|
| 25 |
|
| 26 |
-
[*Note 2*: Some operating systems
|
| 27 |
distinguish between native format and generic format arguments. This is
|
| 28 |
by design as it simplifies use for operating systems that do not require
|
| 29 |
disambiguation. An implementation for an operating system where
|
| 30 |
disambiguation is required is permitted to distinguish between the
|
| 31 |
formats. — *end note*]
|
|
@@ -44,11 +44,11 @@ differently from paths for directories, the path shall be treated as a
|
|
| 44 |
directory path if its last element is a *directory-separator*, otherwise
|
| 45 |
it shall be treated as a path to a regular file.
|
| 46 |
|
| 47 |
[*Note 4*: A path stores a native format pathname
|
| 48 |
[[fs.path.native.obs]] and acts as if it also stores a generic format
|
| 49 |
-
pathname, related as given below. The implementation
|
| 50 |
generic format pathname based on the native format pathname (and
|
| 51 |
possibly other information) when requested. — *end note*]
|
| 52 |
|
| 53 |
When a path is constructed from or is assigned a single representation
|
| 54 |
separate from any path, the other representation is selected by the
|
|
@@ -66,11 +66,11 @@ the result of converting *p*. — *end note*]
|
|
| 66 |
|
| 67 |
The *native encoding* of an ordinary character string is the operating
|
| 68 |
system dependent current encoding for pathnames [[fs.class.path]]. The
|
| 69 |
*native encoding* for wide character strings is the
|
| 70 |
implementation-defined execution wide-character set encoding
|
| 71 |
-
[[
|
| 72 |
|
| 73 |
For member function arguments that take character sequences representing
|
| 74 |
paths and for member functions returning strings, value type and
|
| 75 |
encoding conversion is performed if the value type of the argument or
|
| 76 |
return value differs from `path::value_type`. For the argument or return
|
|
@@ -84,12 +84,12 @@ determined by its value type:
|
|
| 84 |
return values is performed. For Windows-based operating systems, the
|
| 85 |
native ordinary encoding is determined by calling a Windows API
|
| 86 |
function. — *end note*] \[*Note 7*: This results in behavior
|
| 87 |
identical to other C and C++ standard library functions that perform
|
| 88 |
file operations using ordinary character strings to identify paths.
|
| 89 |
-
Changing this behavior would be surprising and
|
| 90 |
-
prone. — *end note*]
|
| 91 |
- `wchar_t`: The encoding is the native wide encoding. The method of
|
| 92 |
conversion is unspecified. \[*Note 8*: For Windows-based operating
|
| 93 |
systems `path::value_type` is `wchar_t` so no conversion from
|
| 94 |
`wchar_t` value type arguments or to `wchar_t` value type return
|
| 95 |
values is performed. — *end note*]
|
|
|
|
| 21 |
or a pathname in the native format [[fs.class.path]]. Such an argument
|
| 22 |
is taken to be in the generic format if and only if it matches the
|
| 23 |
generic format and is not acceptable to the operating system as a native
|
| 24 |
path.
|
| 25 |
|
| 26 |
+
[*Note 2*: Some operating systems have no unambiguous way to
|
| 27 |
distinguish between native format and generic format arguments. This is
|
| 28 |
by design as it simplifies use for operating systems that do not require
|
| 29 |
disambiguation. An implementation for an operating system where
|
| 30 |
disambiguation is required is permitted to distinguish between the
|
| 31 |
formats. — *end note*]
|
|
|
|
| 44 |
directory path if its last element is a *directory-separator*, otherwise
|
| 45 |
it shall be treated as a path to a regular file.
|
| 46 |
|
| 47 |
[*Note 4*: A path stores a native format pathname
|
| 48 |
[[fs.path.native.obs]] and acts as if it also stores a generic format
|
| 49 |
+
pathname, related as given below. The implementation can generate the
|
| 50 |
generic format pathname based on the native format pathname (and
|
| 51 |
possibly other information) when requested. — *end note*]
|
| 52 |
|
| 53 |
When a path is constructed from or is assigned a single representation
|
| 54 |
separate from any path, the other representation is selected by the
|
|
|
|
| 66 |
|
| 67 |
The *native encoding* of an ordinary character string is the operating
|
| 68 |
system dependent current encoding for pathnames [[fs.class.path]]. The
|
| 69 |
*native encoding* for wide character strings is the
|
| 70 |
implementation-defined execution wide-character set encoding
|
| 71 |
+
[[character.seq]].
|
| 72 |
|
| 73 |
For member function arguments that take character sequences representing
|
| 74 |
paths and for member functions returning strings, value type and
|
| 75 |
encoding conversion is performed if the value type of the argument or
|
| 76 |
return value differs from `path::value_type`. For the argument or return
|
|
|
|
| 84 |
return values is performed. For Windows-based operating systems, the
|
| 85 |
native ordinary encoding is determined by calling a Windows API
|
| 86 |
function. — *end note*] \[*Note 7*: This results in behavior
|
| 87 |
identical to other C and C++ standard library functions that perform
|
| 88 |
file operations using ordinary character strings to identify paths.
|
| 89 |
+
Changing this behavior would be surprising and
|
| 90 |
+
error-prone. — *end note*]
|
| 91 |
- `wchar_t`: The encoding is the native wide encoding. The method of
|
| 92 |
conversion is unspecified. \[*Note 8*: For Windows-based operating
|
| 93 |
systems `path::value_type` is `wchar_t` so no conversion from
|
| 94 |
`wchar_t` value type arguments or to `wchar_t` value type return
|
| 95 |
values is performed. — *end note*]
|