Home
last modified time | relevance | path

Searched refs:escaped (Results 1 – 15 of 15) sorted by relevance

/ndk/sources/third_party/googletest/googletest/src/
Dgtest-port.cc228 bool AtomMatchesChar(bool escaped, char pattern_char, char ch) { in AtomMatchesChar() argument
229 if (escaped) { // "\\p" where p is pattern_char. in AtomMatchesChar()
321 bool escaped, char c, char repeat, const char* regex, in MatchRepetitionAndRegexAtHead() argument
338 if (str[i] == '\0' || !AtomMatchesChar(escaped, c, str[i])) in MatchRepetitionAndRegexAtHead()
357 const bool escaped = *regex == '\\'; in MatchRegexAtHead() local
358 if (escaped) in MatchRegexAtHead()
365 escaped, regex[0], regex[1], regex + 2, str); in MatchRegexAtHead()
370 return (*str != '\0') && AtomMatchesChar(escaped, *regex, *str) && in MatchRegexAtHead()
Dgtest-internal-inl.h945 GTEST_API_ bool AtomMatchesChar(bool escaped, char pattern, char ch);
949 bool escaped, char ch, char repeat, const char* regex, const char* str);
/ndk/sources/host-tools/make-3.81/tests/scripts/features/
Descape38 # TEST 4: This one should fail, since the escape char is escaped.
51 # TEST 6: Test escaped comments
/ndk/sources/third_party/googletest/googletest/
DCHANGES10 * Improvement: char pointers and char arrays are now escaped properly
/ndk/sources/host-tools/make-3.81/tests/
DNEWS29 A new test for escaped :'s in filenames (someone on VMS found this
DChangeLog478 * scripts/features/escape: Test handling of escaped comment
666 * scripts/features/escape: Add a test for backslash-escaped spaces
/ndk/sources/host-tools/sed-4.2.1/doc/
Dsed.texi492 each must be escaped by a backslash (@code{\}).
511 each must be escaped by a backslash (@code{\}).
853 because it is escaped.
1155 lists, provide that each instance is escaped by a @code{\}.
1225 are printed in C-style escaped form; long lines are split,
2979 these to be escaped if you want them to behave as special characters,
3004 Backreferences must still be escaped when using extended regular
3073 On one hand Perl introduces several more escaped sequences
3095 @cindex Perl-style regular expressions, escaped sequences
3105 just note that if the character that follows the escaped digit
[all …]
Dsed-in.texi491 each must be escaped by a backslash (@code{\}).
510 each must be escaped by a backslash (@code{\}).
852 because it is escaped.
1154 lists, provide that each instance is escaped by a @code{\}.
1224 are printed in C-style escaped form; long lines are split,
2812 these to be escaped if you want them to behave as special characters,
2837 Backreferences must still be escaped when using extended regular
2906 On one hand Perl introduces several more escaped sequences
2928 @cindex Perl-style regular expressions, escaped sequences
2938 just note that if the character that follows the escaped digit
[all …]
Dsed.info359 be escaped by a backslash (`\').
375 delimiter characters, each must be escaped by a backslash (`\').
620 because it is escaped.
827 DEST-CHARS lists, provide that each instance is escaped by a `\'.
874 characters (and the `\' character) are printed in C-style escaped
2193 (`{}'). While basic regular expressions require these to be escaped if
2217 Backreferences must still be escaped when using extended regular
/ndk/sources/host-tools/sed-4.2.1/testsuite/
DBOOST.tests74 ; now try escaped brackets:
/ndk/sources/host-tools/sed-4.2.1/
DNEWS195 * fix incorrect parsing of ^ after escaped (.
/ndk/sources/host-tools/make-3.81/
DNEWS202 before assignment. This means that escaped dollar signs ($$ etc.)
DChangeLog2416 there's no need to do it again, and doing so strips escaped $'s.
/ndk/sources/host-tools/make-3.81/doc/
Dmake.info-1873 escaped by another backslash will continue the comment across
1410 (escaped) variable reference is simply unescaped, without being
1458 escaped:
Dmake.texi1005 escaped by another backslash will continue the comment across multiple
1643 while the second (escaped) variable reference is simply unescaped,
1697 You can also mix functions here, as long as they are properly escaped: