* gdbint.texinfo (Formatting): Mention some formatting guidelines

	for casts and unary operators.

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index b058fa0bd978c5493d390d45209cf6322ec41e45..d10f9123f44d8c313fee50354b4c6825c7773fef 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,8 @@
+2011-02-04  Pedro Alves  <pedro@codesourcery.com>
+
+       * gdbint.texinfo (Formatting): Mention some formatting guidelines
+       for casts and unary operators.
+
 2011-02-04  Tom Tromey  <tromey@redhat.com>
 
        * gdb.texinfo (GDB/MI Async Records): Document that symbols-loaded

diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo
index 8149cb927d9b50b48bc7521e7d9db8e5342fdb2f..a49470708fe74ea96c76f00d1379f30166271fc9 100644 (file)
--- 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