...
ARR36-C. Do not subtract or compare two pointers that do not refer to the same array -started cjohns 4/8
cjohns: this looks done, can you verify and remove from TODO? or if more needs to be done, can you leave it as a comment? thx - alexv 4/17
...
The following rule needs to be completed.
ARR37-C. Do not add or subtract an integer to a pointer to a non-array object -started cjohns 4/8
cjohns: this looks done, can you verify and remove from TODO? or if more needs to be done, can you leave it as a comment? thx - alexv 4/17
...
For FIO39-C. Do not read in from a stream directly following output to that stream Can we rewrite the NCCE and compliant solution as a function or use another mechanism so we don't need to specify the name of the device. Unfortunately device names such as "/dev/device2" appear to be OS specific. Perhaps check this section for other instances of this problem as well.
...
The Risk Assessment Summary tables for each section need to be updated (they are out of date with the actual rules). - I got as far as EXP07, which still has the risk assessment for EXP10
i went through on 4/15 and checked to make sure the section tables matched the rules... are we confident that the risk summaries in the rules are correct? Only one missing and it is FLP02 -alexv 4/17
...
The forward backward navigation links between sections need to be checked and fixed.
...
- what in particular should be written about these? should this go under Signals b/c of SIGFPE or under FLP02 as that is already started? - alexv 4/15
...
I've looked at some of the C rules and recommendations, and here are my
recommendations 
for copying them across to C++.
...