For more items on the TODO list, please see C++ Coding Standard Development Guidelines.
These rules need professional editing:
| Content by Label | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
These rules should be preserved:
| Content by Label | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
These rules should be updated:
| Content by Label | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
These rules should be deleted:
| Content by Label | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
These rules are covered by C and do not require a C++ rule:
| Content by Label | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
These rules have notes associated with them:
| Content by Label | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Incomplete pages in C++ use the incomplete tag. Pages with hidden notes in them use the notes tag.
But C++ rules that were copied from C and not updated are marked with the incomplete-cpp tag.
C++ rules that are accurate, but need their sample code updated (from C) are tagged with the update-code tag.
Incomplete pages in C++ use their own incomplete-cpp tag.
When you copy this rule over to the C++ side:
FIO34-C. Use int to capture the return value of character IO functions
Be sure to add something about istream::get() which return int values, not char values.
Add to the C++ standard rules marked with exportable-c++.
Update forward/back/next links
The Arrays section rules need to include info wrt STL vectors
...
Update references to C (eg C99) to references to C++
Under 'Implmeentation-Specific Details', test compliance with various C++ compilers (update from C compilers)
...
Pages should have tags to indicate the status of their corresponding checker in Compass Rose:
Tag | Meaning |
|---|---|
ROSE catches all violations | |
ROSE catches some violations | |
ROSE could catch some or all violations, but doesn't yet. | |
ROSE doesn't catch violations, but will soon, | |
These rules can't be checked automatically. | |
These rules could be checked automatically in theory, but not by ROSE. | |
ROSE could check these rules if it recognized macro usage. | |
ROSE could check these rules if it recognized derived types in expressions, such as | |
ROSE could check these rules if it operated on multiple files at once. | |
ROSE could enforce this rule, but could not avoid catching some false positives. |
At this point, all rules should have one of these tags. That is, they should be completely or partially checked by ROSE, or they should be marked 'rose-possible', in that we will try to check them with ROSE, or they should have one of the nonapplicable tags indicating we don't think they can be checked with ROSE.
...
There are some rules in other standards that might make good C++ rules. They are tagged exportable-c++. Port to C++ those rules that are truly applicable.
...
review -> review + review-one -> review + review-two -> No tags
significant changes -> review or incompleteMake sure code examples illustrate valid C++ practices (except when illustrating a particular bad example)
...