From 3e30ca7b1cc48afdaf4fd24adeebe08eaff8a47c Mon Sep 17 00:00:00 2001 From: Tony Finch Date: Tue, 10 Sep 2002 10:54:39 +0000 Subject: [PATCH] Remove a sentence about wrapping macro definitions in bare braces, which became wrong after using do { } while (0) became recommended. Move the definition of what braces are to their new first occurrence. Reviewed by: bde --- share/man/man9/style.9 | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/share/man/man9/style.9 b/share/man/man9/style.9 index 0f6c59b6aa56..c48c32fc9318 100644 --- a/share/man/man9/style.9 +++ b/share/man/man9/style.9 @@ -162,11 +162,6 @@ all in lowercase and the macro has the same name all in uppercase. .\" same and you #undef the macro (if any) to get the function. .\" It is not followed for MALLOC(), and not very common if inline .\" functions are used. -If a -macro needs more than a single line, use braces -.Ql ( \&{ -and -.Ql \&} ) . Right-justify the backslashes; it makes it easier to read. If the macro encapsulates a compound statement, enclose it in a @@ -376,7 +371,11 @@ comment. .Pp Space after keywords .Pq Ic if , while , for , return , switch . -No braces are +No braces +.Ql ( \&{ +and +.Ql \&} ) +are used for control statements with zero or only a single statement unless that statement is more than a single line in which case they are permitted. Forever loops are done with