mirror of
https://github.com/isocpp/CppCoreGuidelines.git
synced 2024-03-22 13:30:58 +08:00
Corrected typographical error...
This commit is contained in:
parent
2a50e98a19
commit
1652fb6d56
|
@ -11384,7 +11384,7 @@ A `char*` that points to something that is not a C-style string (e.g., a pointer
|
||||||
There is no really good way to say "pointer to a single `char` (`string_view{p,1}` can do that, and `T*` where `T` is a `char` in a template that has not been specialized for C-style strings).
|
There is no really good way to say "pointer to a single `char` (`string_view{p,1}` can do that, and `T*` where `T` is a `char` in a template that has not been specialized for C-style strings).
|
||||||
|
|
||||||
* `zstring` // a `char*` supposed to be a C-style string; that is, a zero-terminated sequence of `char` or `null_ptr`
|
* `zstring` // a `char*` supposed to be a C-style string; that is, a zero-terminated sequence of `char` or `null_ptr`
|
||||||
* `czstring` // a `const char*` supposed to be a C-style string; that is, a zero-terminated sequence of `const` `char` ort `null_ptr`
|
* `czstring` // a `const char*` supposed to be a C-style string; that is, a zero-terminated sequence of `const` `char` or `null_ptr`
|
||||||
|
|
||||||
Logically, those last two aliases are not needed, but we are not always logical,
|
Logically, those last two aliases are not needed, but we are not always logical,
|
||||||
and they make the distinction between a pointer to one `char` and a pointer to a C-style string explicit.
|
and they make the distinction between a pointer to one `char` and a pointer to a C-style string explicit.
|
||||||
|
|
Loading…
Reference in New Issue
Block a user