OpenE2K
/
qemu-e2k
13
4
Fork 0
Code Issues 4 Pull Requests Projects 2 Releases Activity

CODING_STYLE: update mixed declaration rules 

Mixed declarations do come in handy at the top of #ifdef blocks.
Reluctantly allow this particular usage and suggest an alternative.

Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
This commit is contained in:
Paolo Bonzini 2015-06-19 09:28:13 +02:00
parent d4ba8cb0a1
commit 690a35e1f2
1 changed files with 9 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
CODING_STYLE
View File

@ -87,10 +87,15 @@ Furthermore, it is the QEMU coding style.
5. Declarations 5. Declarations
Mixed declarations (interleaving statements and declarations within blocks) Mixed declarations (interleaving statements and declarations within
are not allowed; declarations should be at the beginning of blocks. In other blocks) are generally not allowed; declarations should be at the beginning
words, the code should not generate warnings if using GCC's of blocks.
-Wdeclaration-after-statement option.
Every now and then, an exception is made for declarations inside a
#ifdef or #ifndef block: if the code looks nicer, such declarations can
be placed at the top of the block even if there are statements above.
On the other hand, however, it's often best to move that #ifdef/#ifndef
block to a separate function altogether.
6. Conditional statements 6. Conditional statements