summaryrefslogtreecommitdiff
path: root/CODING_STYLE
diff options
context:
space:
mode:
authorPeter Maydell <peter.maydell@linaro.org>2012-01-13 20:29:49 +0000
committerStefan Hajnoczi <stefanha@linux.vnet.ibm.com>2012-02-10 10:44:51 +0000
commite3c52bf2e59a1caa7a8f4d1eb069cc1406075d10 (patch)
tree51e8afde95b6ebd2b3901f4e40ba27e1bee89473 /CODING_STYLE
parenta6f79cc9a5efc34c5b751b2e866a4977259f3f63 (diff)
CODING_STYLE: Clarify style for enum and function type names
Clarify that enum type names and function type names should follow the CamelCase style used for structured type names. Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Diffstat (limited to 'CODING_STYLE')
-rw-r--r--CODING_STYLE3
1 files changed, 2 insertions, 1 deletions
diff --git a/CODING_STYLE b/CODING_STYLE
index 6e61c49089..7c82d4d0af 100644
--- a/CODING_STYLE
+++ b/CODING_STYLE
@@ -44,7 +44,8 @@ Rationale:
3. Naming
Variables are lower_case_with_underscores; easy to type and read. Structured
-type names are in CamelCase; harder to type but standing out. Scalar type
+type names are in CamelCase; harder to type but standing out. Enum type
+names and function type names should also be in CamelCase. Scalar type
names are lower_case_with_underscores_ending_with_a_t, like the POSIX
uint64_t and family. Note that this last convention contradicts POSIX
and is therefore likely to be changed.