Cpp Coding Standards/Principles
This topic contains high level rules - or more general guidelines - that are good advice, but may be more difficult to check or decide in some cases. Aspects of them may be implemented by many of the other standards rules.
Correctness, simplicity and clarity first.
Hide as much information as you can.
Design orthogonally. Every change of a single aspect should need a code change only in one location.
Establish a rational error handling policy for the OpenOffice.org in general.
Write code such that unit tests are possible. For complex data structures provide possibilities to stream them out into a human understandable form.