| /external/mesa3d/src/gallium/auxiliary/tgsi/ |
| D | tgsi_text.c | 449 struct parsed_bracket *brackets) in parse_register_bracket() argument
454 memset(brackets, 0, sizeof(struct parsed_bracket)); in parse_register_bracket()
459 if (parse_file( &cur, &brackets->ind_file )) { in parse_register_bracket()
460 if (!parse_register_1d( ctx, &brackets->ind_file, in parse_register_bracket()
461 &brackets->ind_index )) in parse_register_bracket()
471 brackets->ind_comp = TGSI_SWIZZLE_X; in parse_register_bracket()
474 brackets->ind_comp = TGSI_SWIZZLE_Y; in parse_register_bracket()
477 brackets->ind_comp = TGSI_SWIZZLE_Z; in parse_register_bracket()
480 brackets->ind_comp = TGSI_SWIZZLE_W; in parse_register_bracket()
491 parse_int( &ctx->cur, &brackets->index ); in parse_register_bracket()
[all …]
|
| /external/owasp/sanitizer/src/main/org/owasp/html/ |
| D | CssTokens.java | 75 public final Brackets brackets; field in CssTokens
112 int end = brackets.partner(tokenIndex); in spliceToEnd()
175 String normalizedCss, Brackets brackets, int[] tokenBreaks, in CssTokens() argument
178 this.brackets = brackets; in CssTokens()
250 private final int[] brackets; field in CssTokens.Brackets
252 private Brackets(int[] brackets) { in Brackets() argument
253 this.brackets = brackets; in Brackets()
260 return brackets[(bracketIndex << 1) + 1]; in partner()
266 int right = brackets.length >> 1; in bracketIndexForToken()
269 int value = brackets[mid << 1]; in bracketIndexForToken()
[all …]
|
| /external/markdown/MarkdownTest/Tests_2007/ |
| D | Links, inline style.text | 11 [URL wrapped in angle brackets](</url/>).
13 [URL w/ angle brackets + title](</url/> "Here's the title").
|
| D | Links, reference style.text | 11 With [embedded [brackets]] [b].
51 [Something in brackets like [this][] should work]
|
| D | Markdown Documentation - Syntax.text | 125 and `&`. Left angle brackets are used to start tags; ampersands are
162 angle brackets as delimiters for HTML tags, Markdown will treat them as
171 However, inside Markdown code spans and blocks, angle brackets and
499 Within a code block, ampersands (`&`) and angle brackets (`<` and `>`)
503 ampersands and angle brackets. For example, this:
550 In both styles, the link text is delimited by [square brackets].
574 Reference-style links use a second set of square brackets, inside
579 You can optionally use a space to separate the sets of brackets:
590 * Square brackets containing the link identifier (optionally
598 The link URL may, optionally, be surrounded by angle brackets:
[all …]
|
| D | Markdown Documentation - Basics.text | 49 Blockquotes are indicated using email-style '`>`' angle brackets.
190 *reference*. With both styles, you use square brackets to delimit the
266 backtick quotes. Any ampersands (`&`) and angle brackets (`<` or
|
| /external/markdown/tests/extensions-x-toc/ |
| D | syntax-toc.txt | 88 and `&`. Left angle brackets are used to start tags; ampersands are
125 angle brackets as delimiters for HTML tags, Markdown will treat them as
134 However, inside Markdown code spans and blocks, angle brackets and
462 Within a code block, ampersands (`&`) and angle brackets (`<` and `>`)
466 ampersands and angle brackets. For example, this:
513 In both styles, the link text is delimited by [square brackets].
537 Reference-style links use a second set of square brackets, inside
542 You can optionally use a space to separate the sets of brackets:
553 * Square brackets containing the link identifier (optionally
561 The link URL may, optionally, be surrounded by angle brackets:
[all …]
|
| /external/markdown/tests/markdown-test/ |
| D | links-reference.txt | 11 With [embedded [brackets]] [b].
|
| D | markdown-syntax.txt | 125 and `&`. Left angle brackets are used to start tags; ampersands are
162 angle brackets as delimiters for HTML tags, Markdown will treat them as
171 However, inside Markdown code spans and blocks, angle brackets and
499 Within a code block, ampersands (`&`) and angle brackets (`<` and `>`)
503 ampersands and angle brackets. For example, this:
550 In both styles, the link text is delimited by [square brackets].
574 Reference-style links use a second set of square brackets, inside
579 You can optionally use a space to separate the sets of brackets:
590 * Square brackets containing the link identifier (optionally
598 The link URL may, optionally, be surrounded by angle brackets:
[all …]
|
| D | markdown-documentation-basics.txt | 49 Blockquotes are indicated using email-style '`>`' angle brackets.
190 *reference*. With both styles, you use square brackets to delimit the
266 backtick quotes. Any ampersands (`&`) and angle brackets (`<` or
|
| /external/markdown/MarkdownTest/Tests_2004/ |
| D | Links, reference style.text | 11 With [embedded [brackets]] [b].
|
| D | Markdown Documentation - Syntax.text | 125 and `&`. Left angle brackets are used to start tags; ampersands are
162 angle brackets as delimiters for HTML tags, Markdown will treat them as
171 However, inside Markdown code spans and blocks, angle brackets and
499 Within a code block, ampersands (`&`) and angle brackets (`<` and `>`)
503 ampersands and angle brackets. For example, this:
550 In both styles, the link text is delimited by [square brackets].
574 Reference-style links use a second set of square brackets, inside
579 You can optionally use a space to separate the sets of brackets:
590 * Square brackets containing the link identifier (optionally
598 The link URL may, optionally, be surrounded by angle brackets:
[all …]
|
| D | Markdown Documentation - Basics.text | 49 Blockquotes are indicated using email-style '`>`' angle brackets.
190 *reference*. With both styles, you use square brackets to delimit the
266 backtick quotes. Any ampersands (`&`) and angle brackets (`<` or
|
| /external/markdown/tests/extensions-x-def_list/ |
| D | markdown-syntax.txt | 125 and `&`. Left angle brackets are used to start tags; ampersands are
162 angle brackets as delimiters for HTML tags, Markdown will treat them as
171 However, inside Markdown code spans and blocks, angle brackets and
499 Within a code block, ampersands (`&`) and angle brackets (`<` and `>`)
503 ampersands and angle brackets. For example, this:
550 In both styles, the link text is delimited by [square brackets].
574 Reference-style links use a second set of square brackets, inside
579 You can optionally use a space to separate the sets of brackets:
590 * Square brackets containing the link identifier (optionally
598 The link URL may, optionally, be surrounded by angle brackets:
[all …]
|
| /external/pdfium/testing/resources/ |
| D | trailer_unterminated.in | 26 % closing angle-brackets not present for trailer dictionary.
|
| /external/harfbuzz_ng/test/shaping/ |
| D | hb_test_tools.py | 309 brackets = l[i] + l[j]
311 if brackets == '()':
313 elif brackets == '<>':
315 elif brackets == '[]':
|
| /external/autotest/client/site_tests/hardware_StorageFio/ |
| D | 8k_async_randwrite | 5 # The job name in brackets must match the name of this file.
|
| /external/vogar/ |
| D | .vogarconfig.example | 6 # .vogarconfig file. Names contained in angle brackets are placeholders.
|
| /external/dtc/Documentation/ |
| D | dts-format.txt | 35 * Arrays are represented by angle brackets surrounding a space separated list
60 * A bytestring is enclosed in square brackets [] with each byte
|
| /external/markdown/docs/extensions/ |
| D | Fenced_Code_Blocks.txt | 37 brackets:
|
| /external/clang/test/SemaObjC/ |
| D | parameterized_classes.m | 242 …ObjCStringRef> typeArgsProtocolQualsConflict1; // expected-error{{angle brackets contain both a ty…
243 …g, NSString *> typeArgsProtocolQualsConflict2; // expected-error{{angle brackets contain both a ty…
244 …e, NSString *> typeArgsProtocolQualsConflict3; // expected-error{{angle brackets contain both a ty…
246 …g, NSString *> typeArgsProtocolQualsConflict5; // expected-error{{angle brackets contain both a ty…
|
| /external/pcre/dist2/ |
| D | HACKING | 432 A pair of non-capturing round brackets is wrapped round each expression at
433 compile time, so alternation always happens in the context of brackets.
439 Non-capturing brackets use the opcode OP_BRA, capturing brackets use OP_CBRA. A
443 to the next one, or to the OP_KET opcode. For capturing brackets, the bracket
478 Possessive brackets
492 OP_ONCE or OP_ONCE_NC. The former is used when there are no capturing brackets
565 recursions are automatically wrapped inside OP_ONCE brackets, because otherwise
567 brackets, but it is nevertheless still treated as an atomic group.
|
| /external/vulkan-validation-layers/tests/gtest-1.7.0/ |
| D | configure.ac | 4 # integers separated by periods and surrounded by square brackets (e.g.
|
| /external/googletest/googletest/ |
| D | configure.ac | 4 # integers separated by periods and surrounded by square brackets (e.g.
|
| /external/protobuf/gtest/ |
| D | configure.ac | 4 # integers separated by periods and surrounded by square brackets (e.g.
|