use PCRE syntax instead of the beautiful new (?i ...) syntax

This commit is contained in:
Vern Paxson 2018-06-29 13:01:05 -07:00
parent 726424f371
commit 85c4b0d285
6 changed files with 12 additions and 14 deletions

View file

@ -256,9 +256,8 @@ Here is a more detailed description of each type:
a "foo", "Foo", "BaR", etc.
You can also introduce a case-insensitive sub-pattern by enclosing it
in ``(+i``<pattern>``)``. For clarity, you can optionally include
trailing whitespace after the ``+i`` designator. So, for example,
``/foo|(+i bar)/`` will match "foo" and "BaR", but *not* "Foo".
in ``(?i:``<pattern>``)``. So, for example, ``/foo|(?i:bar)/`` will
match "foo" and "BaR", but *not* "Foo".
For both ways of specifying case-insensitivity, characters enclosed
in double quotes maintain their case-sensitivity. So for example