From e3c52bf2e59a1caa7a8f4d1eb069cc1406075d10 Mon Sep 17 00:00:00 2001 From: Peter Maydell Date: Fri, 13 Jan 2012 20:29:49 +0000 Subject: 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 Signed-off-by: Stefan Hajnoczi --- CODING_STYLE | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'CODING_STYLE') 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. -- cgit v1.2.1