documentation: coding style, existing file names

Existing file names should not be changed without a reason.

Signed-off-by: Jan Iversen <jan@casacondor.com>
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
This commit is contained in:
jan Iversen 2019-12-25 10:32:07 +01:00 committed by Dirk Hohndel
parent 0241155e47
commit 9c0a22ef76

View file

@ -101,6 +101,8 @@ other editors that implement this coding style, please add them here.
* there is a strong preference for lower case file names; sometimes conventions
or outside requirements make camelCase filenames the better (or only) choice,
but absent such an outside reason all file names should be lower case
This rule applies to new file names, existing file names should not be
changed without a reason.
* cpp/h file names should usually be identical to the class name but in lower
case. Where it seems appropriate, multiple, closely related classes can be