You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 294 Next »

Pages that need work have an incomplete tag.
Pages that need to be deleted have a deleteme tag.
Pages that have problems with the citations at the bottom have the citations-incomplete tag.
Pages with comments that might make good sidebars are tagged as sidebar


review -> review + review-one -> review + review-two -> No tags
significant changes -> review or incomplete


There is some inconsistency with the use of const. We used to have a recommendation that declarations appear like this:

int const *ip;

But we eventually got rid of it. Most of our declarations are of this form, but some are of this form:

const int *ip;

The argument we had was that the first form is less prone to error, but the second form is widely used, and not something that people will change.

Our choices are a) apply the first style consistently, b) apply the second style consistently, c) allow a mix of both styles.

Whatever style we adopt should also apply to other qualified type declarations, like volatile.

The bot changes all of these to have rightmost const. There are very few (if any, it would only be what was added recently) the other way. -jp


C++ has it's own TODO List


Pages now have tags to indicate the status of their corresponding checker in Compass Rose:

Tag

Meaning

rose-complete

ROSE catches all violations

rose-partial

ROSE catches some violations

rose-possible

ROSE could catch some or all violations, but doesn't yet.

rose-gcc

ROSE doesn't catch violations, but will soon, GCC catches violations

unenforceable

These rules can't be checked automatically.

rose-na

These rules could be checked automatically in theory, but not by ROSE.

rose-na-macros

ROSE could check these rules if it recognized macro usage.

rose-na-exptypes

ROSE could check these rules if it recognized derived types in expressions, such as size_t.

rose-na-multiple-files

ROSE could check these rules if it operated on multiple files at once.

rose-false-positive | ROSE could enforce this rule, but could not avoid catching some false positives. |

At this point, all rules with priority level L1 or L2 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.


It might also be worth giving these another look.


  • No labels