Blame CodingGuideLines.txt
|
Packit |
8c9aa0 |
CppUnit's coding guidelines for portability:
|
|
Packit |
8c9aa0 |
--------------------------------------------
|
|
Packit |
8c9aa0 |
|
|
Packit |
8c9aa0 |
- don't explicitly declare CppUnit namespace, instead use macro
|
|
Packit |
8c9aa0 |
CPPUNIT_NS_BEGIN and CPPUNIT_NS_END.
|
|
Packit |
8c9aa0 |
|
|
Packit |
8c9aa0 |
- don't explicitly use 'CppUnit' to refer to class in CppUnit namespace,
|
|
Packit |
8c9aa0 |
instead use macro CPPUNIT_NS which expands to either 'CppUnit' or
|
|
Packit |
8c9aa0 |
nothing depending on the configuration.
|
|
Packit |
8c9aa0 |
|
|
Packit |
8c9aa0 |
- don't use the 'using directive', always use full qualification. For STL,
|
|
Packit |
8c9aa0 |
always use std::.
|
|
Packit |
8c9aa0 |
|
|
Packit |
8c9aa0 |
- don't use the mutable keyword, instead do a const cast.
|
|
Packit |
8c9aa0 |
|
|
Packit |
8c9aa0 |
- don't use default parameter value in template function. Not supported
|
|
Packit |
8c9aa0 |
by all compiler (on OS/390 for instance).
|
|
Packit |
8c9aa0 |
|
|
Packit |
8c9aa0 |
As such, usage of those features should always be optional.
|
|
Packit |
8c9aa0 |
|
|
Packit |
8c9aa0 |
CppUnit's version control system management
|
|
Packit |
8c9aa0 |
--------------------------------------------
|
|
Packit |
8c9aa0 |
|
|
Packit |
8c9aa0 |
- only commit patches that are known to build; other commits might just be reverted
|
|
Packit |
8c9aa0 |
to allow bisecting
|
|
Packit |
8c9aa0 |
|
|
Packit |
8c9aa0 |
- work in feature branches until your feature is ready to merge, if the feature
|
|
Packit |
8c9aa0 |
may break the build ask for review on the libreoffice developer mailing list
|
|
Packit |
8c9aa0 |
|
|
Packit |
8c9aa0 |
- new features and patches without bug report only in master
|
|
Packit |
8c9aa0 |
and not in stable branches
|