StarMirror/CppCoreGuidelines
1
0
Fork 0
mirror of https://github.com/isocpp/CppCoreGuidelines.git synced 2024-03-22 13:30:58 +08:00
Code Issues Projects Releases Wiki Activity

Merge pull request #171 from RicoAntonioFelix/master

Browse Source 
Corrected typographical errors...
This commit is contained in:
Gabriel Dos Reis 2015-09-27 09:56:52 -07:00
commit 12ee68f8d2
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CppCoreGuidelines.md
View File

@ -11383,7 +11383,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.
@ -11489,7 +11489,7 @@ More specific and detailed rules are easier to enforce.
**Reason**: Compilers do not read comments. **Reason**: Compilers do not read comments.
Comments are less precise than code. Comments are less precise than code.
Comments are not updates as consistently as code. Comments are not updated as consistently as code.
**Example, bad**: **Example, bad**: