mirror of
https://github.com/subsurface/subsurface.git
synced 2025-02-19 22:16:15 +00:00
documentation: coding style cpp/h names
Add rule about cpp/h names [Dirk Hohndel: small edits to the rule] Signed-off-by: Jan Iversen <jan@casacondor.com> Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
This commit is contained in:
parent
4ef1e9cb28
commit
0241155e47
1 changed files with 4 additions and 0 deletions
|
@ -102,6 +102,10 @@ other editors that implement this coding style, please add them here.
|
||||||
or outside requirements make camelCase filenames the better (or only) choice,
|
or outside requirements make camelCase filenames the better (or only) choice,
|
||||||
but absent such an outside reason all file names should be lower case
|
but absent such an outside reason all file names should be lower case
|
||||||
|
|
||||||
|
* 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
|
||||||
|
in a single file with a more generic name.
|
||||||
|
|
||||||
* switch statements with blocks are a little bit special (to avoid indenting
|
* switch statements with blocks are a little bit special (to avoid indenting
|
||||||
too far)
|
too far)
|
||||||
```
|
```
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue