[PATCH] [doc] Insert space before open-paren in C code fragments.

[Thien-Thi Nguyen]

Greetings,

This is a tiny change to keep the internal consistency,
you know, internally consistent...

BTW, i had to wrestle a bit w/ the time-stamp (line 6)
to avoid "febbraio 16, 2010".  Perhaps one could add:

 system-time-locale: "C"

to the local variables block at EOF?

thi

________________________________________________

>From 5e098f2be4bffefb5118157a833f2aaa6980a0a3 Mon Sep 17 00:00:00 2001
From: Thien-Thi Nguyen <address@hidden>
Date: Tue, 16 Feb 2010 07:23:35 +0100
Subject: [PATCH] [doc] Insert space before open-paren in C code fragments.

* doc/standards.texi
(Conditional Compilation): Say "if (...)", not "if( ...)".
(Semantics): Say "fd = open (...)", not "fd = open(...)".

Signed-off-by: Thien-Thi Nguyen <address@hidden>
---
 doc/standards.texi |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/standards.texi b/doc/standards.texi
index cbf2f84..7960880 100644
--- a/doc/standards.texi
+++ b/doc/standards.texi
@@ -3,7 +3,7 @@
 @setfilename standards.info
 @settitle GNU Coding Standards
 @c This date is automagically updated when you save this file:
address@hidden lastupdate December 11, 2009
address@hidden lastupdate February 16, 2010
 @c %**end of header
 
 @dircategory GNU organization
@@ -509,7 +509,7 @@ @node Conditional Compilation
 GCC developers many hours, or even days, per year.
 
 In the case of function-like macros like @code{REVERSIBLE_CC_MODE} in
-GCC which cannot be simply used in @code{if( ...)} statements, there is
+GCC which cannot be simply used in @code{if (...)} statements, there is
 an easy workaround.  Simply introduce another macro
 @code{HAS_REVERSIBLE_CC_MODE} as in the following example:
 
@@ -690,7 +690,7 @@ @node Semantics
 avoid this problem by creating temporary files in this manner:
 
 @example
-fd = open(filename, O_WRONLY | O_CREAT | O_EXCL, 0600);
+fd = open (filename, O_WRONLY | O_CREAT | O_EXCL, 0600);
 @end example
 
 @noindent
-- 
1.6.3.2