Mirrors/CppCoreGuidelines
1
0
Fork 0
mirror of https://github.com/isocpp/CppCoreGuidelines.git synced 2025-12-17 12:44:42 +03:00
Code Issues Actions Packages Projects Releases Wiki Activity

Remove spaces before ptr-declarators in examples

Browse Source
This commit is contained in:
Jonathan Wakely
2017-05-04 09:48:19 +01:00
parent f0239407ad
commit bdb5d27a10
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
CppCoreGuidelines.md
View File

@@ -7227,13 +7227,13 @@ the former (`dynamic_cast`) is far harder to implement correctly in general.
Consider: Consider:
struct B { struct B {
const char * name {"B"}; const char* name {"B"};
virtual const char* id() const { return name; } virtual const char* id() const { return name; }
// ... // ...
}; };
struct D : B { struct D : B {
const char * name {"D"}; const char* name {"D"};
const char* id() const override { return name; } const char* id() const override { return name; }
// ... // ...
}; };
@@ -12717,7 +12717,7 @@ If a `thread` joins, we can safely pass pointers to objects in the scope of the
##### Example ##### Example
void f(int * p) void f(int* p)
{ {
// ... // ...
*p = 99; *p = 99;
@@ -12756,7 +12756,7 @@ If a `thread` is detached, we can safely pass pointers to static and free store
##### Example ##### Example
void f(int * p) void f(int* p)
{ {
// ... // ...
*p = 99; *p = 99;
@@ -17523,7 +17523,7 @@ See also
Note how `>>` and `!=` are provided for `string` (as examples of useful operations) and there are no explicit Note how `>>` and `!=` are provided for `string` (as examples of useful operations) and there are no explicit
allocations, deallocations, or range checks (`string` takes care of those). allocations, deallocations, or range checks (`string` takes care of those).
In C++17, we might use `string_view` as the argument, rather than `const string *` to allow more flexibility to callers: In C++17, we might use `string_view` as the argument, rather than `const string*` to allow more flexibility to callers:
vector<string> read_until(string_view terminator) // C++17 vector<string> read_until(string_view terminator) // C++17
{ {