mirror of
https://gitlab.freedesktop.org/cairo/cairo.git
synced 2026-05-17 21:48:07 +02:00
Fix spelling errors.
This commit is contained in:
parent
5699072035
commit
97ac61700a
2 changed files with 7 additions and 3 deletions
|
|
@ -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.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,7 @@
|
|||
2005-06-03 Carl Worth <cworth@cworth.org>
|
||||
|
||||
* CODING_STYLE: Fix spelling errors.
|
||||
|
||||
2005-06-03 Carl Worth <cworth@cworth.org>
|
||||
|
||||
* CODING_STYLE: Fix Freudian unwrapped line in paragraph
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue