Commit e3c52bf2 authored by Peter Maydell's avatar Peter Maydell Committed by Stefan Hajnoczi
Browse files

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: default avatarPeter Maydell <peter.maydell@linaro.org>
Signed-off-by: default avatarStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
parent a6f79cc9

CODING_STYLE

+2 −1
Original line number Diff line number Diff line
@@ -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.