/prebuilts/ndk/8/platforms/android-14/arch-x86/usr/include/ |
fts.h | 92 #define FTS_F 8 /* regular file */
|
/prebuilts/ndk/8/platforms/android-8/arch-arm/usr/include/ |
fts.h | 92 #define FTS_F 8 /* regular file */
|
/prebuilts/ndk/8/platforms/android-9/arch-arm/usr/include/ |
fts.h | 92 #define FTS_F 8 /* regular file */
|
/prebuilts/ndk/8/platforms/android-9/arch-mips/usr/include/ |
fts.h | 92 #define FTS_F 8 /* regular file */
|
/prebuilts/ndk/8/platforms/android-9/arch-x86/usr/include/ |
fts.h | 92 #define FTS_F 8 /* regular file */
|
/sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/editors/layout/gle2/ |
Gesture.java | 50 * the drag source is no longer informed of mouse updates, whereas a regular
|
/sdk/eclipse/plugins/com.android.ide.eclipse.tests/ |
README.txt | 64 Note: this method runs the tests within a regular JVM environment (ie not within
|
/system/extras/tests/sdcard/ |
sysutil.h | 70 // 0: a regular process. Should die on OOM.
|
/ndk/sources/host-tools/nawk-20071023/ |
FIXES | 112 fixed a bug in regular expressions that dates (so help me) from 1977; 133 regular expressions in non-US locales. thanks to ruslan for keeping 145 regular expressions (cclenter). its properties are much too 154 for regular expressions, where the goal is to match specific 583 to permit regular expressions to be much bigger. 729 Added \x to regular expressions (already in strings). 731 Centralized the code for parsing escapes in regular expressions. [all...] |
/external/clang/utils/ |
FindSpecRefs | 535 ('28 Regular expressions library', '1000'), 538 ('28.3 Regular expressions summary', '1002'), 546 ('28.11Regular expression algorithms', '1029'), 547 ('28.12Regular expression Iterators', '1033'), 548 ('28.13Modified ECMAScript regular expression grammar', '1039'), [all...] |
/external/libvpx/libvpx/examples/includes/PHP-Markdown-Extra-1.2.3/ |
PHP Markdown Extra Readme.text | 288 * Item 1 (regular paragraph) 383 * Fixed a performance problem where the regular expression for strong 413 * Fixed a performance problem where the regular expression for strong 451 * Added the missing TextileRestricted method that was added to regular 567 * Made the block-level HTML parser smarter using a specially-crafted regular
|
/external/markdown/MarkdownTest/Tests_2004/ |
Markdown Documentation - Syntax.text | 98 This is a regular paragraph. 106 This is another regular paragraph. 516 Regular Markdown syntax is not processed within code blocks. E.g., 552 To create an inline link, use a set of regular parentheses immediately 823 use regular HTML `<img>` tags.
|
/external/markdown/MarkdownTest/Tests_2007/ |
Markdown Documentation - Syntax.text | 98 This is a regular paragraph. 106 This is another regular paragraph. 516 Regular Markdown syntax is not processed within code blocks. E.g., 552 To create an inline link, use a set of regular parentheses immediately 823 use regular HTML `<img>` tags.
|
/external/markdown/docs/ |
writing_extensions.txt | 65 one of its children. Each pattern object uses a single regular expression and 70 Returns a compiled regular expression. 77 Note that any regular expression returned by ``getCompiledRegExp`` must capture 80 provided in the ``Pattern`` you can pass in a regular expression without that 199 regular expression.
|
/external/markdown/tests/extensions-x-def_list/ |
markdown-syntax.txt | 98 This is a regular paragraph. 106 This is another regular paragraph. 516 Regular Markdown syntax is not processed within code blocks. E.g., 552 To create an inline link, use a set of regular parentheses immediately 823 use regular HTML `<img>` tags.
|
/external/markdown/tests/extensions-x-toc/ |
syntax-toc.txt | 61 This is a regular paragraph. 69 This is another regular paragraph. 479 Regular Markdown syntax is not processed within code blocks. E.g., 515 To create an inline link, use a set of regular parentheses immediately 786 use regular HTML `<img>` tags.
|
/external/markdown/tests/markdown-test/ |
markdown-syntax.txt | 98 This is a regular paragraph. 106 This is another regular paragraph. 516 Regular Markdown syntax is not processed within code blocks. E.g., 552 To create an inline link, use a set of regular parentheses immediately 823 use regular HTML `<img>` tags.
|
/prebuilts/tools/common/proguard/proguard4.7/docs/ |
downloads.html | 142 <li>Fixed handling of regular expressions with only negators. 144 <li>Fixed regular expression pattern for constructors in ReTrace. 162 regular expressions to parse stack traces. 407 <li>Extended regular expressions for class names to comma-separated lists. 474 using regular <code>-injars</code> options, using filters if necessary.
|
/external/libvpx/libvpx/examples/includes/geshi/docs/ |
geshi-doc.txt | 93 + 4.3.8 Using Regular Expressions 498 As of version 1.0.2, GeSHi comes with a contrib/ directory, which in it contains a "wizard" script for creating a stylesheet. Although this script is by no means a complete solution, it will create the necessary rules for the basic lexics - comments, strings for example. Things not included in the wizard include regular expressions for any language that uses them (PHP and XML are two languages that use them), and keyword-link styles. However, this script should take some of the tedium out of the job of making an external stylesheet. Expect a much better version of this script in version 1.2! [all...] |
/frameworks/base/docs/html/training/design-navigation/ |
example-wireframe-tablet.svg | [all...] |
/external/chromium/testing/gtest/include/gtest/internal/ |
gtest-port.h | 53 // GTEST_HAS_POSIX_RE - Define it to 1/0 to indicate that POSIX regular 146 // Regular expressions: 147 // RE - a simple regular expression class using the POSIX 148 // Extended Regular Expression syntax on UNIX-like 149 // platforms, or a reduced regular exception syntax on 261 // Defines this to true iff Google Test can use POSIX regular expressions. 792 // Regular Expression syntax. 814 // FullMatch(str, re) returns true iff regular expression re matches 816 // PartialMatch(str, re) returns true iff regular expression re [all...] |
/external/gtest/include/gtest/internal/ |
gtest-port.h | 53 // GTEST_HAS_POSIX_RE - Define it to 1/0 to indicate that POSIX regular 149 // Regular expressions: 150 // RE - a simple regular expression class using the POSIX 151 // Extended Regular Expression syntax on UNIX-like 152 // platforms, or a reduced regular exception syntax on 265 // Defines this to true iff Google Test can use POSIX regular expressions. 826 // Regular Expression syntax. 848 // FullMatch(str, re) returns true iff regular expression re matches 850 // PartialMatch(str, re) returns true iff regular expression re [all...] |
/external/icu4c/test/cintltst/ |
reapits.c | 11 /*C API TEST FOR Regular Expressions */ 13 * This is an API test for ICU regular expressions in C. It doesn't test very many cases, and doesn't 17 * More complete testing of regular expression functionality is done with the C++ tests. 47 * 're" is the compiled, ready-to-go regular expression. 175 * regular expression user callbacks. This test is mostly the same as 196 * Regular Expression C API Tests 210 log_data_err("Failed to open regular expression, %s:%d, error is \"%s\" (Are you missing data?)\n", __FILE__, __LINE__, u_errorName(status)); [all...] |
/external/libvpx/libvpx/third_party/googletest/src/include/gtest/internal/ |
gtest-port.h | 53 // GTEST_HAS_POSIX_RE - Define it to 1/0 to indicate that POSIX regular 149 // Regular expressions: 150 // RE - a simple regular expression class using the POSIX 151 // Extended Regular Expression syntax on UNIX-like 152 // platforms, or a reduced regular exception syntax on 266 // Defines this to true iff Google Test can use POSIX regular expressions. 808 // Regular Expression syntax. 830 // FullMatch(str, re) returns true iff regular expression re matches 832 // PartialMatch(str, re) returns true iff regular expression re [all...] |
/external/llvm/utils/unittest/googletest/include/gtest/internal/ |
gtest-port.h | 53 // GTEST_HAS_POSIX_RE - Define it to 1/0 to indicate that POSIX regular 150 // Regular expressions: 151 // RE - a simple regular expression class using the POSIX 152 // Extended Regular Expression syntax on UNIX-like 153 // platforms, or a reduced regular exception syntax on 269 // Defines this to true iff Google Test can use POSIX regular expressions. 813 // Regular Expression syntax. 835 // FullMatch(str, re) returns true iff regular expression re matches 837 // PartialMatch(str, re) returns true iff regular expression re [all...] |