Home
last modified time | relevance | path

Searched refs:regexes (Results 1 – 25 of 33) sorted by relevance

12

/openbsd/gnu/usr.bin/perl/dist/Filter-Simple/
H A DChanges36 strings, or regexes
66 - Re-allowed user-defined terminators to be regexes
81 - Added note about use of /m flag when using ^ or $ in filter regexes
/openbsd/gnu/llvm/lld/Common/
H A DErrorHandler.cpp174 static std::regex regexes[] = { in getLocation() local
193 for (std::regex &re : regexes) { in getLocation()
/openbsd/gnu/llvm/clang/utils/
H A Dcreduce-clang-crash.py132 regexes = [r"Assertion .+ failed", # Linux assert()
141 for msg_re in regexes:
/openbsd/gnu/llvm/lldb/docs/use/
H A Dlinks.rst73 A collection of LLDB aliases/regexes and Python scripts.
/openbsd/gnu/usr.bin/perl/cpan/perlfaq/lib/
H A Dperlfaq6.pod164 Do not use regexes. Use a module and forget about the
172 X<$/, regexes in> X<$INPUT_RECORD_SEPARATOR, regexes in>
173 X<$RS, regexes in>
606 =head2 What does it mean that regexes are greedy? How can I get around it?
609 Most people mean that greedy regexes match as much as they can.
740 a single regex that matches a list of literal strings (not regexes).
923 =head2 Are Perl regexes DFAs or NFAs? Are they POSIX compliant?
H A Dperlfaq.pod884 What does it mean that regexes are greedy? How can I get around it?
916 Are Perl regexes DFAs or NFAs? Are they POSIX compliant?
H A Dperlglossary.pod149 A X<assertions (in regexes), defined>X<regular expressions, assertions
1954 An B<assertion> that X<lookahead assertions>X<assertions (in regexes),
1959 An B<assertion> X<lookbehind assertions>X<assertions (in regexes),
3783 (in regexes), zero–width>subpattern B<assertion> matching the B<null
/openbsd/gnu/usr.bin/perl/pod/
H A Dperlrequick.pod8 using regular expressions ('regexes') in Perl.
109 With all of the regexes above, if the regex matched anywhere in the
537 regexes, see L<perlretut> and for the reference page, see L<perlre>.
H A Dperlsource.pod98 C<if>, basic file reads and writes, simple regexes, etc. These are run
H A Dperlunicook.pod128 strings and regexes). In v5.16, there is an implicit
408 properties for use in regexes.
H A Dperlfilter.pod565 regexes with embedded newlines that are specified with raw C</.../>
569 regexes specified with raw C<?...?> delimiters may cause mysterious
H A Dperlreref.pod402 for details on regexes and internationalisation.
H A Dperl5101delta.pod113 types (coderefs, hashes, regexes). Thus, writers of overloading routines
1315 Various leaks associated with named captures in regexes have been fixed
1688 Some regexes may run much more slowly when run in a child thread compared
H A Dperlreguts.pod33 When speaking about regexes we need to distinguish between their source
386 that perl's regexes have. For instance when parsing C</x(?:foo)y/>,
H A Dperldebtut.pod381 of code or regexes until the cows come home:
H A Dperl5120delta.pod396 complex types (coderefs, hashes, regexes). Thus, writers of overloading
2662 Various leaks associated with named captures in regexes have been fixed
3051 Some regexes may run much more slowly when run in a child thread compared
H A Dperlre.pod870 for regexes compiled within the scope of C<use locale>, and C</d> was
1194 interpolate regexes into larger regexes and not have to worry about the
1835 function in .NET regexes, the behavior is not. In Perl the groups are
H A Dperldebug.pod161 Use C<~pattern> and C<!pattern> for positive and negative regexes.
H A Dperl5140delta.pod559 In certain circumstances, C<\400>-C<\777> in regexes have behaved
612 =head3 Stringification of regexes has changed
620 Code that needs to work properly with both old- and new-style regexes
H A Dperl5260delta.pod2768 Certain regexes making use of the experimental C<regex_sets> feature could
3231 Fixed issues with recursive regexes. The behavior was fixed in Perl 5.24.
/openbsd/gnu/usr.bin/perl/dist/Module-CoreList/
H A DChanges852 - corelist utility accepts regexes as arguments, eg. /IPC::Open/
853 - Errors when building regexes are trapped and warning is generated
/openbsd/gnu/usr.bin/perl/cpan/IPC-Cmd/t/
H A D01_IPC-Cmd.t52 { ### list of commands and regexes matching output
/openbsd/gnu/llvm/libcxx/docs/Status/
H A DCxx14Issues.csv144 …wg2332>`__","regex_iterator/regex_token_iterator should forbid temporary regexes","Issaquah","|Com…
/openbsd/gnu/llvm/clang/docs/
H A DUsersManual.rst2855 .. option:: -fprofile-filter-files=[regexes]
2857 Define a list of regexes separated by a semi-colon.
2858 If a file name matches any of the regexes then the file is instrumented.
2866 .. option:: -fprofile-exclude-files=[regexes]
2868 Define a list of regexes separated by a semi-colon.
2869 If a file name doesn't match all the regexes then the file is instrumented.
2878 of the regexes from ``-fprofile-filter-list`` and doesn't match all the regexes
4250 …Instrument only functions from files where names don't match all the regexes separated by a semi-c…
/openbsd/gnu/usr.bin/perl/t/op/
H A Dtr.t964 { # [perl #38293] chr(65535) should be allowed in regexes

12