summaryrefslogtreecommitdiff
path: root/CODING_STYLE
diff options
context:
space:
mode:
authorCarl Worth <cworth@cworth.org>2005-06-03 15:56:52 +0000
committerCarl Worth <cworth@cworth.org>2005-06-03 15:56:52 +0000
commit97ac61700ae8d2fcf055fdad12533671895f539b (patch)
tree154d9899604367f778f406589c977381e4aca4ef /CODING_STYLE
parent56990720358ea18b026f952101ddd674a5fbb268 (diff)
Fix spelling errors.
Diffstat (limited to 'CODING_STYLE')
-rw-r--r--CODING_STYLE6
1 files changed, 3 insertions, 3 deletions
diff --git a/CODING_STYLE b/CODING_STYLE
index f1a7b1c32..04fc53c44 100644
--- a/CODING_STYLE
+++ b/CODING_STYLE
@@ -68,7 +68,7 @@ the optional braces should not usually appear:
else
do_that ();
-But the braces are mandatory when mixing single statement and compund
+But the braces are mandatory when mixing single statement and compound
statements in the various clauses. For example, do not do this:
if (condition) {
@@ -92,7 +92,7 @@ better with the braces:
do_something ();
}
-And note that this last example also shows a situtation in which the
+And note that this last example also shows a situation in which the
opening brace really needs to be on its own line. The following looks awful:
if (condition &&
@@ -169,7 +169,7 @@ and names so that the names are aligned:
align_parameter_names_in_prototypes (const char *char_star_arg,
int int_arg,
double *double_star_arg,
- double duble_arg);
+ double double_arg);
Note that parameters with a * prefix are aligned one character to the
left so that the actual names are aligned.