Searched refs:braces (Results 1 – 25 of 47) sorted by relevance
12
| /mirbsd/src/gnu/usr.bin/texinfo/makeinfo/ |
| D | footnote.c | 158 int braces = 1; in cm_footnote() local
161 while (braces) in cm_footnote()
170 braces++; in cm_footnote()
172 braces--; in cm_footnote()
|
| /mirbsd/src/gnu/usr.sbin/sendmail/libmilter/ |
| D | smfi.c | 795 char braces[4]; local
809 braces[0] = '{';
810 braces[1] = *symname;
811 braces[2] = '}';
812 braces[3] = '\0';
815 braces[0] = '\0';
829 if (braces[0] != '\0' && strcmp(*s, braces) == 0)
|
| /mirbsd/src/share/doc/psd/23.Cknr/ |
| D | cman3 | 474 consists of an expression or a list of values nested in braces.
491 or when the rest of the initializer is enclosed in braces.
504 it consists of a single expression, perhaps in braces.
|
| D | cman1 | 249 would indicate an optional expression in braces.
|
| /mirbsd/src/usr.bin/vi/docs/tutorial/ |
| D | vi.advanced | 11 Another point to remember is that commands are surrounded by curly-braces and
15 surrounded by curly-braces on the section line where that command is
598 of curly braces since the command itself contains a curly brace - we
895 notation. Using curly braces to surround command strings works fine as
896 long as the command string does not contain any curly braces itself.
897 However, the curly braces are legitimate commands in vi. Therefore, for
898 any command sequence that contains curly braces, we will surround that
899 sequence with SQUARE braces, as on the previous Section line.)
|
| D | vi.beginner | 65 We will adopt the notation of putting commands in curly braces so we can write
69 that the curly braces are NOT part of the command string you are to type. Do
70 NOT type the curly braces.
72 Sometimes, the command string in the curly braces will be rather long, and may
|
| /mirbsd/src/gnu/usr.bin/perl/pod/ |
| D | perlsyn.pod | 170 For C<next>, just double the braces:
205 But generally, a block is delimited by curly brackets, also known as braces.
325 they aren't loops. You can double the braces to make them such, though.
|
| D | perlref.pod | 129 Because curly brackets (braces) are used for several other things
130 including BLOCKs, you may occasionally have to disambiguate braces at the
355 though, you could use parentheses instead of braces. That's not the case.
|
| D | perlintro.pod | 267 (i.e. a bunch of statements surrounded by curly-braces) in which they
316 Note that the braces are required in Perl, even if you've only got one
|
| D | perldsc.pod | 266 tightly than the postfix subscripting brackets or braces! This will no
717 # careful of extra block braces on fh ref
|
| D | perldata.pod | 338 As in some shells, you can enclose the variable name in braces to
350 Without the braces, Perl would have looked for a $whospeak, a
469 braces as above.
|
| D | perltrap.pod | 659 String interpolation of the C<$#array> construct differs when braces
1381 =item * Arbitrary expressions are evaluated inside braces within double quotes
1383 Perl now sometimes evaluates arbitrary expressions inside braces that occur
|
| D | perlform.pod | 164 one line if enclosed in braces. If so, the opening brace must be the first
|
| D | perlreftut.pod | 159 You can always use an array reference, in curly braces, in place of
|
| D | perlfaq4.pod | 592 function inside the braces used to dereference a reference. If we
599 more work. We can really have any code we like inside the braces, so
601 that is up to you, and you can use code inside the braces.
|
| D | perlunicode.pod | 145 hexadecimal, should be placed in the braces. For instance, a smiley
154 character name within the braces, such as C<\N{WHITE SMILING FACE}>.
|
| D | perlmod.pod | 41 Use braces to disambiguate, as in C<"This is ${owner}'s house">.
|
| D | perl5004delta.pod | 1386 parentheses shown here; braces are also frequently used.)
1414 delimiters than the parentheses shown here; braces are also frequently
|
| D | perlglossary.pod | 330 L<statements|/statement> that is delimited by braces. The C<if> and
335 delimited by braces.
625 example, a pair of braces acts as a composer for a hash, and a pair of
720 A bare, single L</statement>, without any braces, hanging off an C<if>
|
| D | perlfaq6.pod | 64 describes this. For example, the C<s///> above uses braces as
|
| /mirbsd/src/gnu/usr.bin/perl/jpl/docs/ |
| D | Tutorial.pod | 330 declared C<perl> and use double curly braces to make life easier on
785 Use double, rather than single, curly braces ({{ and }}).
|
| /mirbsd/src/gnu/usr.bin/binutils/gas/doc/ |
| D | c-xtensa.texi | 115 braces:
129 Directives and labels are not allowed inside the braces of a FLIX
|
| /mirbsd/src/bin/mksh/ |
| D | check.t | 2798 name: single-quotes-in-braces
2807 name: single-quotes-in-quoted-braces
2817 name: single-quotes-in-braces-nested
2836 name: single-quotes-in-heredoc-braces
2848 name: single-quotes-in-nested-braces
2858 name: single-quotes-in-nested-quoted-braces
2868 name: single-quotes-in-nested-braces-nested
2887 name: single-quotes-in-heredoc-nested-braces
11133 name: case-braces
|
| /mirbsd/src/gnu/usr.bin/binutils/etc/ |
| D | standards.texi | 2121 @cindex braces, in C source
2125 for open-braces in column zero to find the beginnings of C functions.
2427 @code{if} statement, always put braces around the @code{if}-@code{else}.
2463 or write the nested @code{if} within braces like this:
|
| /mirbsd/src/gnu/usr.bin/binutils/gdb/doc/ |
| D | rluser.texi | 1274 @item complete-into-braces (M-@{)
1276 enclosed within braces so the list is available to the shell
|
12