From 9c0a22ef76bc9be58b369f30d20e334b80acf06f Mon Sep 17 00:00:00 2001 From: jan Iversen Date: Wed, 25 Dec 2019 10:32:07 +0100 Subject: documentation: coding style, existing file names Existing file names should not be changed without a reason. Signed-off-by: Jan Iversen Signed-off-by: Dirk Hohndel --- CODINGSTYLE.md | 2 ++ 1 file changed, 2 insertions(+) (limited to 'CODINGSTYLE.md') diff --git a/CODINGSTYLE.md b/CODINGSTYLE.md index 0c2f38a67..15cde9435 100644 --- a/CODINGSTYLE.md +++ b/CODINGSTYLE.md @@ -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 -- cgit v1.2.3-70-g09d2