re PR other/9813 (misplaced paragraph in Constructing Calls node)
PR doc-bug/9813 * doc/extend.texi: Move misplaced paragraph about underscores in variables in macros. From-SVN: r64666
This commit is contained in:
parent
cd41c847e7
commit
526278c97f
@ -1,3 +1,9 @@
|
||||
2003-03-21 Volker Reichelt <reichelt@igpm.rwth-aachen.de>
|
||||
|
||||
PR doc-bug/9813
|
||||
* doc/extend.texi: Move misplaced paragraph about underscores in
|
||||
variables in macros.
|
||||
|
||||
2003-03-21 Eric Botcazou <ebotcazou@libertysurf.fr>
|
||||
Richard Henderson <rth@redhat.com>
|
||||
|
||||
|
@ -887,19 +887,6 @@ the containing function. You should specify, for @var{result}, a value
|
||||
returned by @code{__builtin_apply}.
|
||||
@end deftypefn
|
||||
|
||||
@cindex underscores in variables in macros
|
||||
@cindex @samp{_} in variables in macros
|
||||
@cindex local variables in macros
|
||||
@cindex variables, local, in macros
|
||||
@cindex macros, local variables in
|
||||
|
||||
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 @code{a} and @code{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.
|
||||
|
||||
@node Typeof
|
||||
@section Referring to a Type with @code{typeof}
|
||||
@findex typeof
|
||||
@ -950,6 +937,19 @@ arithmetic type and evaluates each of its arguments exactly once:
|
||||
_a > _b ? _a : _b; @})
|
||||
@end example
|
||||
|
||||
@cindex underscores in variables in macros
|
||||
@cindex @samp{_} in variables in macros
|
||||
@cindex local variables in macros
|
||||
@cindex variables, local, in macros
|
||||
@cindex macros, local variables in
|
||||
|
||||
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 @code{a} and @code{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.
|
||||
|
||||
@noindent
|
||||
Some more examples of the use of @code{typeof}:
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user