| /external/littlemock/src/com/google/testing/littlemock/ |
| AppDataDirGuesser.java | 78 // Strip out the bit between angle brackets, that's our path.
|
| /external/llvm/lib/Support/ |
| regerror.c | 65 { REG_EBRACK, "REG_EBRACK", "brackets ([ ]) not balanced" },
|
| /external/markdown/markdown/extensions/ |
| abbr.py | 67 Note: we force each char as a literal match (in brackets) as we don't
|
| /external/protobuf/gtest/test/ |
| gtest_xml_output_unittest_.cc | 91 FAIL() << "Invalid characters in brackets [\x1\x2]";
|
| /external/webkit/Source/JavaScriptCore/tests/mozilla/js1_2/Objects/ |
| toString-001.js | 105 return false; // should begin and end with curly brackets
|
| /external/webkit/Source/JavaScriptCore/tests/mozilla/js1_5/Expressions/ |
| shell.js | 70 * e) Add square brackets to the beginning and end of the string
|
| /libcore/luni/src/main/java/org/w3c/dom/ |
| DocumentType.java | 74 * This is does not contain the delimiting square brackets.
|
| /ndk/sources/host-tools/ndk-stack/regex/ |
| regerror.c | 60 { REG_EBRACK, "REG_EBRACK", "brackets ([ ]) not balanced" },
|
| /ndk/sources/host-tools/sed-4.2.1/testsuite/ |
| uniq.good | 47 /* "Once" brackets are like assertion brackets except that after a match,
54 /* Assertion brackets. Check the alternative branches in turn - the
80 /* For extended extraction brackets (large number), we have to fish out
81 /* For extended extraction brackets (large number), we have to fish out the
204 a move back into the brackets. Check the alternative branches in turn - the
222 brackets - for testing for empty matches
223 brackets started but not finished, we have to save their starting points
409 i.e. it could be ()* or ()? in the pattern. Brackets with fixed upper
[all...] |
| /external/apache-xml/src/main/java/org/apache/xalan/templates/ |
| OutputProperties.java | 290 * into a string with the namespace in curly brackets.
333 * into a string with the namespace in curly brackets.
398 * into strings with the namespace in curly brackets.
411 * into strings with the namespace in curly brackets.
495 // of a tokenizer so I can track whitespace inside of curly brackets,
|
| /external/chromium/googleurl/src/ |
| gurl.h | 251 // surrounded by square brackets, like "[2001:db8::1]". To exclude these
252 // brackets, use HostNoBrackets() below.
318 // Returns the host, excluding the square brackets surrounding IPv6 address
|
| /external/markdown/MarkdownTest/Tests_2004/ |
| Markdown Documentation - Basics.html | 41 <p>Blockquotes are indicated using email-style '<code>></code>' angle brackets.</p>
187 <em>reference</em>. With both styles, you use square brackets to delimit the
271 backtick quotes. Any ampersands (<code>&</code>) and angle brackets (<code><</code> or
|
| Markdown Documentation - Basics.text-out | 50 angle brackets.</p>
193 and <em>reference</em>. With both styles, you use square brackets
275 angle brackets (<code><</code> or <code>></code>) will
|
| Markdown Documentation - Basics.text-res | 50 angle brackets.</p>
193 and <em>reference</em>. With both styles, you use square brackets
275 angle brackets (<code><</code> or <code>></code>) will
|
| /external/markdown/MarkdownTest/Tests_2007/ |
| Markdown Documentation - Basics.html | 41 <p>Blockquotes are indicated using email-style '<code>></code>' angle brackets.</p>
187 <em>reference</em>. With both styles, you use square brackets to delimit the
271 backtick quotes. Any ampersands (<code>&</code>) and angle brackets (<code><</code> or
|
| /external/markdown/tests/markdown-test/ |
| markdown-documentation-basics.html | 33 <p>Blockquotes are indicated using email-style '<code>></code>' angle brackets.</p>
150 <em>reference</em>. With both styles, you use square brackets to delimit the
208 backtick quotes. Any ampersands (<code>&</code>) and angle brackets (<code><</code> or
|
| /development/host/windows/usb/ |
| NOTICE | 181 boilerplate notice, with the fields enclosed by brackets "[]"
183 the brackets!) The text should be enclosed in the appropriate
|
| /development/scripts/app_engine_server/ |
| LICENSE | 182 boilerplate notice, with the fields enclosed by brackets "[]"
184 the brackets!) The text should be enclosed in the appropriate
|
| /development/tools/apkcheck/src/com/android/apkcheck/ |
| TypeUtils.java | 69 /* if we found an array, strip the brackets off */
253 * nested brackets, but we're not expecting to see multiple instances
|
| /external/android-mock/ |
| LICENSE.txt | 182 boilerplate notice, with the fields enclosed by brackets "[]"
184 the brackets!) The text should be enclosed in the appropriate
|
| /external/antlr/antlr-3.4/runtime/Delphi/Sources/Antlr3.Runtime/ |
| Antlr.Runtime.Collections.pas | 139 /// they are returned by its enumerator, enclosed in curly brackets ("{}").
151 /// they are returned by its enumerator, enclosed in square brackets ("[]").
|
| /external/chromium/sdch/open-vcdiff/ |
| COPYING | 182 boilerplate notice, with the fields enclosed by brackets "[]"
184 the brackets!) The text should be enclosed in the appropriate
|
| /external/chromium/sdch/open-vcdiff/packages/deb/ |
| copyright | 188 boilerplate notice, with the fields enclosed by brackets "[]"
190 the brackets!) The text should be enclosed in the appropriate
|
| /external/chromium/testing/gmock/scripts/generator/ |
| COPYING | 182 boilerplate notice, with the fields enclosed by brackets "[]"
184 the brackets!) The text should be enclosed in the appropriate
|
| /external/chromium/testing/gtest/test/ |
| gtest_xml_output_unittest.py | 89 <failure message="Failed
Invalid characters in brackets []" type=""><![CDATA[gtest_xml_output_unittest_.cc:*
91 Invalid characters in brackets []%(stack)s]]></failure>
|
