mirror of
https://github.com/sigmasternchen/php-doc-en
synced 2025-03-16 00:48:54 +00:00
No need to explicitly specify list numbers and letters here.
They are implicit using the <orderedlist>... git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@63868 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
parent
aca8823f8f
commit
5b5e1f4a4b
1 changed files with 13 additions and 13 deletions
|
@ -1,5 +1,5 @@
|
|||
<?xml version="1.0" encoding="iso-8859-1"?>
|
||||
<!-- $Revision: 1.64 $ -->
|
||||
<!-- $Revision: 1.65 $ -->
|
||||
<reference id="ref.pcre">
|
||||
<title>Regular Expression Functions (Perl-Compatible)</title>
|
||||
<titleabbrev>PCRE</titleabbrev>
|
||||
|
@ -947,7 +947,7 @@ $fl_array = preg_grep ("/^(\d+)?\.\d+$/", $array);
|
|||
</listitem>
|
||||
<listitem>
|
||||
<simpara>
|
||||
3. Capturing subpatterns that occur inside negative looka-
|
||||
Capturing subpatterns that occur inside negative looka-
|
||||
head assertions are counted, but their entries in the
|
||||
offsets vector are never set. Perl sets its numerical vari-
|
||||
ables from any such patterns that are matched before the
|
||||
|
@ -958,7 +958,7 @@ $fl_array = preg_grep ("/^(\d+)?\.\d+$/", $array);
|
|||
</listitem>
|
||||
<listitem>
|
||||
<simpara>
|
||||
4. Though binary zero characters are supported in the sub-
|
||||
Though binary zero characters are supported in the sub-
|
||||
ject string, they are not allowed in a pattern string
|
||||
because it is passed as a normal C string, terminated by
|
||||
zero. The escape sequence "\0" can be used in the pattern to
|
||||
|
@ -967,7 +967,7 @@ $fl_array = preg_grep ("/^(\d+)?\.\d+$/", $array);
|
|||
</listitem>
|
||||
<listitem>
|
||||
<simpara>
|
||||
5. The following Perl escape sequences are not supported:
|
||||
The following Perl escape sequences are not supported:
|
||||
\l, \u, \L, \U, \E, \Q. In fact these are implemented by
|
||||
Perl's general string-handling and are not part of its pat-
|
||||
tern matching engine.
|
||||
|
@ -975,19 +975,19 @@ $fl_array = preg_grep ("/^(\d+)?\.\d+$/", $array);
|
|||
</listitem>
|
||||
<listitem>
|
||||
<simpara>
|
||||
6. The Perl \G assertion is not supported as it is not
|
||||
The Perl \G assertion is not supported as it is not
|
||||
relevant to single pattern matches.
|
||||
</simpara>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<simpara>
|
||||
7. Fairly obviously, PCRE does not support the (?{code})
|
||||
Fairly obviously, PCRE does not support the (?{code})
|
||||
construction.
|
||||
</simpara>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<simpara>
|
||||
8. There are at the time of writing some oddities in Perl
|
||||
There are at the time of writing some oddities in Perl
|
||||
5.005_02 concerned with the settings of captured strings
|
||||
when part of a pattern is repeated. For example, matching
|
||||
"aba" against the pattern /^(a(b)?)+$/ sets $2 to the value
|
||||
|
@ -1001,7 +1001,7 @@ $fl_array = preg_grep ("/^(\d+)?\.\d+$/", $array);
|
|||
</listitem>
|
||||
<listitem>
|
||||
<simpara>
|
||||
9. Another as yet unresolved discrepancy is that in Perl
|
||||
Another as yet unresolved discrepancy is that in Perl
|
||||
5.005_02 the pattern /^(a)?(?(1)a|b)+$/ matches the string
|
||||
"a", whereas in PCRE it does not. However, in both Perl and
|
||||
PCRE /^(a)?a/ matched against "a" leaves $1 unset.
|
||||
|
@ -1009,12 +1009,12 @@ $fl_array = preg_grep ("/^(\d+)?\.\d+$/", $array);
|
|||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
10. PCRE provides some extensions to the Perl regular
|
||||
PCRE provides some extensions to the Perl regular
|
||||
expression facilities:
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<simpara>
|
||||
(a) Although lookbehind assertions must match fixed length
|
||||
Although lookbehind assertions must match fixed length
|
||||
strings, each alternative branch of a lookbehind assertion
|
||||
can match a different length of string. Perl 5.005 requires
|
||||
them all to have the same length.
|
||||
|
@ -1022,7 +1022,7 @@ $fl_array = preg_grep ("/^(\d+)?\.\d+$/", $array);
|
|||
</listitem>
|
||||
<listitem>
|
||||
<simpara>
|
||||
(b) If <link linkend="pcre.pattern.modifiers">PCRE_DOLLAR_ENDONLY</link> is set and
|
||||
If <link linkend="pcre.pattern.modifiers">PCRE_DOLLAR_ENDONLY</link> is set and
|
||||
<link linkend="pcre.pattern.modifiers">PCRE_MULTILINE</link> is not
|
||||
set, the $ meta- character matches only at the very end of
|
||||
the string.
|
||||
|
@ -1030,13 +1030,13 @@ $fl_array = preg_grep ("/^(\d+)?\.\d+$/", $array);
|
|||
</listitem>
|
||||
<listitem>
|
||||
<simpara>
|
||||
(c) If <link linkend="pcre.pattern.modifiers">PCRE_EXTRA</link> is set, a backslash followed by a letter
|
||||
If <link linkend="pcre.pattern.modifiers">PCRE_EXTRA</link> is set, a backslash followed by a letter
|
||||
with no special meaning is faulted.
|
||||
</simpara>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<simpara>
|
||||
(d) If <link linkend="pcre.pattern.modifiers">PCRE_UNGREEDY</link> is set, the greediness of the repeti-
|
||||
If <link linkend="pcre.pattern.modifiers">PCRE_UNGREEDY</link> is set, the greediness of the repeti-
|
||||
tion quantifiers is inverted, that is, by default they are
|
||||
not greedy, but if followed by a question mark they are.
|
||||
</simpara>
|
||||
|
|
Loading…
Reference in a new issue