Skip to content

doc: mention binary properties and ascii options #308

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 12, 2023
Merged

doc: mention binary properties and ascii options #308

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 10 additions & 4 deletions doc/pcre2compat.3
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,9 +54,10 @@ interprets them.
7. The Perl escape sequences \ep, \eP, and \eX are supported only if PCRE2 is
built with Unicode support (the default). The properties that can be tested
with \ep and \eP are limited to the general category properties such as Lu and
Nd, script names such as Greek or Han, Bidi_Class, Bidi_Control, and the
derived properties Any and LC (synonym L&). Both PCRE2 and Perl support the Cs
(surrogate) property, but in PCRE2 its use is limited. See the
Nd, the derived properties Any and LC (synonym L&), script names such as Greek
or Han, Bidi_Class, Bidi_Control, and a few binary properties. Both PCRE2 and
Perl support the Cs (surrogate) property, but in PCRE2 its use is limited. See
the
.\" HREF
\fBpcre2pattern\fP
.\"
Expand Down Expand Up @@ -204,6 +205,11 @@ documentation for details. Perl went with 5.10 from recursion to iteration
keeping the intermediate matches on the heap, which is ~10% slower but does not
fall into any stack-overflow limit. PCRE2 made a similar change at release
10.30, and also has many build-time and run-time customizable limits.
.P
21. Unlike Perl, PCRE2 doesn't have character set modifiers and specially no way
to set characters by context just like Perl's "/d". A regular expression using
PCRE2_UTF and PCRE2_UCP will use similar rules to Perl's "/u"; something closer
to "/a" could be selected by adding other PCRE2_EXTRA_ASCII* options on top.
.
.
.SH AUTHOR
Expand All @@ -220,6 +226,6 @@ Cambridge, England.
.rs
.sp
.nf
Last updated: 19 September 2023
Last updated: 12 October 2023
Copyright (c) 1997-2023 University of Cambridge.
.fi
10 changes: 6 additions & 4 deletions doc/pcre2unicode.3
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,9 +42,11 @@ When PCRE2 is built with Unicode support, the escape sequences \ep{..},
\eP{..}, and \eX can be used. This is not dependent on the PCRE2_UTF setting.
The Unicode properties that can be tested are a subset of those that Perl
supports. Currently they are limited to the general category properties such as
Lu for an upper case letter or Nd for a decimal number, the Unicode script
names such as Arabic or Han, Bidi_Class, Bidi_Control, and the derived
properties Any and LC (synonym L&). Full lists are given in the
Lu for an upper case letter or Nd for a decimal number, the derived properties
Any and LC (synonym L&), the Unicode script names such as Arabic or Han,
Bidi_Class, Bidi_Control, and a few binary properties.
.P
The full lists are given in the
.\" HREF
\fBpcre2pattern\fP
.\"
Expand Down Expand Up @@ -478,6 +480,6 @@ Cambridge, England.
.rs
.sp
.nf
Last updated: 04 February 2023
Last updated: 12 October 2023
Copyright (c) 1997-2023 University of Cambridge.
.fi