From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH 2/9] CODING_STYLE: Clarify style for enum and function type names
Date: Fri, 10 Feb 2012 11:34:06 +0000 [thread overview]
Message-ID: <1328873653-10554-3-git-send-email-stefanha@linux.vnet.ibm.com> (raw)
In-Reply-To: <1328873653-10554-1-git-send-email-stefanha@linux.vnet.ibm.com>
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(-)
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.
--
1.7.8.3
next prev parent reply other threads:[~2012-02-10 11:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 11:34 [Qemu-devel] [PULL 0/9] Trivial patches for 28 January to 10 February 2012 Stefan Hajnoczi
2012-02-10 11:34 ` [Qemu-devel] [PATCH 1/9] linux-user: fail execve() if env/args too big Stefan Hajnoczi
2012-02-10 11:34 ` Stefan Hajnoczi [this message]
2012-02-10 11:34 ` [Qemu-devel] [PATCH 3/9] cpu-exec.c: Correct comment about this file and indentation cleanup Stefan Hajnoczi
2012-02-10 11:34 ` [Qemu-devel] [PATCH 4/9] ide: fix compilation errors when DEBUG_IDE is set Stefan Hajnoczi
2012-02-10 11:34 ` [Qemu-devel] [PATCH 5/9] vl.c: Fix typo in variable name Stefan Hajnoczi
2012-02-10 11:34 ` [Qemu-devel] [PATCH 6/9] fmopl: Fix typo in function name Stefan Hajnoczi
2012-02-10 11:34 ` [Qemu-devel] [PATCH 7/9] net: remove extra spaces in help messages Stefan Hajnoczi
2012-02-17 6:34 ` Zhi Yong Wu
2012-02-17 6:53 ` Zhi Yong Wu
2012-02-10 11:34 ` [Qemu-devel] [PATCH 8/9] virtio: Remove unneeded g_free() check in virtio_cleanup() Stefan Hajnoczi
2012-02-10 11:34 ` [Qemu-devel] [PATCH 9/9] linux-user: brk() debugging Stefan Hajnoczi
2012-02-17 13:53 ` [Qemu-devel] [PULL 0/9] Trivial patches for 28 January to 10 February 2012 Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1328873653-10554-3-git-send-email-stefanha@linux.vnet.ibm.com \
--to=stefanha@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).