>Submitter-Id: net
>Originator: Richard Braakman <[EMAIL PROTECTED]>
>Organization: The Debian Project
>Confidential: no
>Synopsis:
>Severity: non-critical
>Priority: low
>Category: other
>Class: doc-bug
>Release: 3.2.2 (Debian) (Debian unstable)
>Environment:
System: Debian GNU/Linux (unstable)
Architecture: i686
host: i386-linux
>Description:
[ Reported to the Debian BTS as report #179363.
Please CC [EMAIL PROTECTED] on replies.
Log of report can be found at http://bugs.debian.org/179363 ]
same on the 3.3 branch.
The node (gcc-3.2.info.gz)"Constructing Calls", in "C Extensions",
has this paragraph at the end:
The reason for using names that start with underscores for the local
variables is to avoid conflicts with variable names that occur within
the expressions that are substituted for `a' and `b'. Eventually we
hope to design a new form of declaration syntax that allows you to
declare variables whose scopes start only after their initializers;
this will be a more reliable way to prevent such conflicts.
This does not make sense in that node, which doesn't describe the
use of any local variables, with or without underscores. The paragraph
seems to belong somewhere in the next node, "Typeof", which contains
this example:
#define max(a,b) \
({ typeof (a) _a = (a); \
typeof (b) _b = (b); \
_a > _b ? _a : _b; })
>How-To-Repeat:
>Fix:
