aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Bremner <david@tethera.net>2016-02-13 13:11:18 -0400
committerDavid Bremner <david@tethera.net>2016-03-04 20:44:57 -0400
commit99a0a90f65f5a98d2562e36b48b3e423233c2eb4 (patch)
tree9b29a3f341e7433df108e035dc45e5332dd79ec6
parent08f35973e3a313c7f38544b6712dcf27f9499f91 (diff)
STYLE: document some rules about variable declarations
No-one seemed opposed to C99 style loop variable declarations. The requirement to declare variables at the top of blocks is maybe a little more contested, but I believe it reflects the status quo.
-rw-r--r--devel/STYLE7
1 files changed, 4 insertions, 3 deletions
diff --git a/devel/STYLE b/devel/STYLE
index 24bd5482..b22d8d35 100644
--- a/devel/STYLE
+++ b/devel/STYLE
@@ -25,9 +25,7 @@ The following nonsense code demonstrates many aspects of the style:
static some_type
function (param_type param, param_type param)
{
- int i;
-
- for (i = 0; i < 10; i++) {
+ for (int i = 0; i < 10; i++) {
int j;
j = i + 10;
@@ -64,6 +62,9 @@ function (param_type param, param_type param)
* Code lines should be less than 80 columns and comments should be
wrapped at 70 columns.
+* Variable declarations should be at the top of a block; C99 style
+ control variable declarations in for loops are also OK.
+
Naming
------