Patchwork [2/9] CODING_STYLE: Clarify style for enum and function type names

login
register
mail settings
Submitter Stefan Hajnoczi
Date Feb. 10, 2012, 11:34 a.m.
Message ID <1328873653-10554-3-git-send-email-stefanha@linux.vnet.ibm.com>
Download mbox | patch
Permalink /patch/140631/
State New
Headers show

Comments

Stefan Hajnoczi - Feb. 10, 2012, 11:34 a.m.
From: Peter Maydell <peter.maydell@linaro.org>

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>
---
 CODING_STYLE |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

Patch

diff --git a/CODING_STYLE b/CODING_STYLE
index 6e61c49..7c82d4d 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.