1. Reorganize C++ section to be consistent with C standard.
2. Suffix convention (all C rules end in -C, Java in -J, and C++ in CPP.
3. Start adding "Other Languages" section that references similar / corresponding rules in other languages.
Incomplete pages in C++ use their own incomplete-cpp tag.
...
I've looked at some of the C rules and recommendations, and here are my
recommendations 
for copying them across to C++.DCL05-A - OK more-or-less as is.
DCL06-A - OK more-or-less as is.
DCL07-A - needs rethinking for C++.
DCL09-A - not appropriate for C++ because of ERR00-A.
DCL10-A - needs some reworking for C++ (note that ISO/IEC 14882-2003
does not use the term "variadic function").
DCL11-A - ditto.
DCL12-A - perhaps needs reworking for C++. DCL30-C - needs reworking for C++.
DCL32-C - what are the C++ requirements on identifier length?
DCL33-C - not applicable?
DCL34-C - OK more-or-
less as is.
DCL35-C - OK more-or-less as is, but need to change printf's in CS.
DCL36-C - needs reworking for C++.EXP00-A - OK more-or-less as is.
EXP01-A - needs different examples.
EXP03-A - needs different examples.
EXP04-A - OK more-or-less as is.
EXP07-A - needs rethinking for C++.
EXP08-A - perhaps already covered by OBJ30-C.
EXP09-A - OK more-or-less as is.
EXP34-C - perhaps covered by DAN34-C.
EXP35-C - this appears to require some rethinking anyway.
EXP36-C - needs some thought for C++.
...
Add to the C++ standard rules marked with exportable-c++.
...
Update references to C (eg C99) to references to C++
...
Under 'Implmeentation-Specific Details', test compliance with various C++ compilers (update from C compilers)