Lines Matching refs:parentheses

1303 parentheses immediately after the macro name.  For example,
1312 of parentheses after it.  If you write just the name, it is left alone.
1328 If you put spaces between the macro name and the parentheses in the
1331 parentheses.
1339 The first two pairs of parentheses in this expansion come from the
1342 consume those parentheses.
1352 between the pair of parentheses in the macro definition that make the
1357 followed by a list of @dfn{actual arguments} in parentheses, separated
1383 such parentheses does not end the argument.  However, there is no
2371 Macro definitions do not have to have balanced parentheses.  By writing
2384 unbalanced open parentheses in a macro body is just confusing, and
2389 @cindex parentheses in macro bodies
2392 above, each occurrence of a macro argument name had parentheses around
2393 it.  In addition, another pair of parentheses usually surround the
2754 by the same parentheses that ought to be used to prevent misnesting of
2763 The extra pair of parentheses prevents the comma in @code{foo}'s
3008 function call parentheses are also treated as zero.
3651 within parentheses, are comma-separated, and can cross physical lines.
3652 Commas within nested parentheses are not treated as argument
3671 whitespace between the parentheses.