mirror of
https://github.com/subsurface/subsurface.git
synced 2025-02-19 22:16:15 +00:00
Coding style: clarify preference for filenames
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
This commit is contained in:
parent
080def7729
commit
4126409310
1 changed files with 4 additions and 0 deletions
|
@ -98,6 +98,10 @@ other editors that implement this coding style, please add them here.
|
||||||
where the two meet, use your best judgment and go for best consistency
|
where the two meet, use your best judgment and go for best consistency
|
||||||
(i.e., where does the variable "originate")
|
(i.e., where does the variable "originate")
|
||||||
|
|
||||||
|
* 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
|
||||||
|
|
||||||
* 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
Reference in a new issue