From cef35b0f37719826fd65c1e2376e6328d30b4171 Mon Sep 17 00:00:00 2001 From: Pedro Alves Date: Fri, 4 Feb 2011 19:10:12 +0000 Subject: [PATCH] * gdbint.texinfo (Formatting): Mention some formatting guidelines for casts and unary operators. --- gdb/doc/ChangeLog | 5 +++++ gdb/doc/gdbint.texinfo | 24 +++++++++++++++++++++++- 2 files changed, 28 insertions(+), 1 deletion(-) diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index b058fa0bd9..d10f9123f4 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,8 @@ +2011-02-04 Pedro Alves + + * gdbint.texinfo (Formatting): Mention some formatting guidelines + for casts and unary operators. + 2011-02-04 Tom Tromey * gdb.texinfo (GDB/MI Async Records): Document that symbols-loaded diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo index 8149cb927d..a49470708f 100644 --- a/gdb/doc/gdbint.texinfo +++ b/gdb/doc/gdbint.texinfo @@ -5785,7 +5785,8 @@ compiler. @cindex source code formatting The standard GNU recommendations for formatting must be followed -strictly. +strictly. Any @value{GDBN}-specific deviation from GNU +recomendations is described below. A function declaration should not have its name in column zero. A function definition should have its name in column zero. @@ -5828,6 +5829,27 @@ void * foo; void* foo; @end smallexample +In addition, whitespace around casts and unary operators should follow +the following guidelines: + +@multitable @columnfractions .2 .2 .8 +@item Use... @tab ...instead of @tab + +@item @code{!x} +@tab @code{! x} +@item @code{~x} +@tab @code{~ x} +@item @code{-x} +@tab @code{- x} +@tab (unary minus) +@item @code{(foo) x} +@tab @code{(foo)x} +@tab (cast) +@item @code{*x} +@tab @code{* x} +@tab (pointer dereference) +@end multitable + @subsection Comments @cindex comment formatting