walkero
/
pcre2
1
0
Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity

doc: fix various typos (#132)

This commit is contained in:
Amin Yahyaabadi 2022-07-08 02:01:46 -07:00 committed by GitHub
parent 4804b00e8f
commit 3e52db5209
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 20 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
ChangeLog
View File

@ -6,27 +6,27 @@ Version 10.41 xx-xxx-2022
------------------------- -------------------------
1. Add fflush() before and after a fork callout in pcre2grep to get its output 1. Add fflush() before and after a fork callout in pcre2grep to get its output
to be the same on all systems. (THere were previously ordering differences in to be the same on all systems. (THere were previously ordering differences in
Alpine Linux). Alpine Linux).
2. Merged patch from @carenas (GitHub #110) for pthreads support in CMake. 2. Merged patch from @carenas (GitHub #110) for pthreads support in CMake.
3. SSF scorecards grumbled about possible overflow in an expression in 3. SSF scorecards grumbled about possible overflow in an expression in
pcre2test. It never would have overflowed in practice, but some casts have been pcre2test. It never would have overflowed in practice, but some casts have been
added and at the some time there's been some tidying of fprints that output added and at the some time there's been some tidying of fprints that output
size_t values. size_t values.
4. PR #94 showed up an unused enum in pcre2_convert.c, which is now removed. 4. PR #94 showed up an unused enum in pcre2_convert.c, which is now removed.
5. Minor code re-arrangement to remove gcc warning about realloc() in 5. Minor code re-arrangement to remove gcc warning about realloc() in
pcre2test. pcre2test.
6. Change a number of int variables that hold buffer and line lengths in 6. Change a number of int variables that hold buffer and line lengths in
pcre2grep to PCRE2_SIZE (aka size_t). pcre2grep to PCRE2_SIZE (aka size_t).
7. Added an #ifdef to cut out a call to PRIV(jit_free) when JIT is not 7. Added an #ifdef to cut out a call to PRIV(jit_free) when JIT is not
supported (even though that function would do nothing in that case) at the supported (even though that function would do nothing in that case) at the
request of a user who doesn't even want to link with pcre_jit_compile.o. Also request of a user who doesn't even want to link with pcre_jit_compile.o. Also
tidied up an untidy #ifdef arrangement in pcre2test. tidied up an untidy #ifdef arrangement in pcre2test.
@ -120,7 +120,7 @@ pattern, the optimizing "must be present for a match" character check was not
being flagged as caseless, causing some matches that should have succeeded to being flagged as caseless, causing some matches that should have succeeded to
fail. fail.
23. Fixed a unicode properrty matching issue in JIT. The character was not 23. Fixed a unicode property matching issue in JIT. The character was not
fully read in caseless matching. fully read in caseless matching.
24. Fixed an issue affecting recursions in JIT caused by duplicated data 24. Fixed an issue affecting recursions in JIT caused by duplicated data
@ -147,10 +147,10 @@ Version 10.39 29-October-2021
honoured if chosen. honoured if chosen.
prtdiff_t is signed, so use a signed type instead, and make sure prtdiff_t is signed, so use a signed type instead, and make sure
that an appropiate width is chosen if pointers are 64bit wide and that an appropriate width is chosen if pointers are 64bit wide and
long is not (ex: Windows 64bit). long is not (ex: Windows 64bit).
IMHO removing the cast (and therefore the positibilty of truncation) IMHO removing the cast (and therefore the possibilty of truncation)
make the code cleaner and the fallback is likely portable enough make the code cleaner and the fallback is likely portable enough
with all 64-bit POSIX systems doing LP64 except for Windows. with all 64-bit POSIX systems doing LP64 except for Windows.
@ -201,7 +201,7 @@ Version 10.38 01-October-2021
----------------------------- -----------------------------
1. Fix invalid single character repetition issues in JIT when the repetition 1. Fix invalid single character repetition issues in JIT when the repetition
is inside a capturing bracket and the bracket is preceeded by character is inside a capturing bracket and the bracket is preceded by character
literals. literals.
2. Installed revised CMake configuration files provided by Jan-Willem Blokland. 2. Installed revised CMake configuration files provided by Jan-Willem Blokland.
@ -441,7 +441,7 @@ now correctly backtracked, so this unnecessary restriction has been removed.
7. Added PCRE2_SUBSTITUTE_MATCHED. 7. Added PCRE2_SUBSTITUTE_MATCHED.
8. Added (?* and (?<* as synonms for (*napla: and (*naplb: to match another 8. Added (?* and (?<* as synonyms for (*napla: and (*naplb: to match another
regex engine. The Perl regex folks are aware of this usage and have made a note regex engine. The Perl regex folks are aware of this usage and have made a note
about it. about it.
@ -872,7 +872,7 @@ Patch by Guillem Jover.
warnings were reported. warnings were reported.
38. Using the clang compiler with sanitizing options causes runtime complaints 38. Using the clang compiler with sanitizing options causes runtime complaints
about truncation for statments such as x = ~x when x is an 8-bit value; it about truncation for statements such as x = ~x when x is an 8-bit value; it
seems to compute ~x as a 32-bit value. Changing such statements to x = 255 ^ x seems to compute ~x as a 32-bit value. Changing such statements to x = 255 ^ x
gets rid of the warnings. There were also two missing casts in pcre2test. gets rid of the warnings. There were also two missing casts in pcre2test.

4
HACKING
View File

@ -212,7 +212,7 @@ META_THEN (*THEN) - no argument (see below for with argument)
The two RANGE values occur only in character classes. They are positioned The two RANGE values occur only in character classes. They are positioned
between two literals that define the start and end of the range. In an EBCDIC between two literals that define the start and end of the range. In an EBCDIC
evironment it is necessary to know whether either of the range values was environment it is necessary to know whether either of the range values was
specified as an escape. In an ASCII/Unicode environment the distinction is not specified as an escape. In an ASCII/Unicode environment the distinction is not
relevant. relevant.
@ -233,7 +233,7 @@ their data in the lower 16 bits of the element. META_RECURSE is followed by an
offset, for use in error messages. offset, for use in error messages.
META_BACKREF is followed by an offset if the back reference group number is 10 META_BACKREF is followed by an offset if the back reference group number is 10
or more. The offsets of the first ocurrences of references to groups whose or more. The offsets of the first occurrences of references to groups whose
numbers are less than 10 are put in cb->small_ref_offset[] (only the first numbers are less than 10 are put in cb->small_ref_offset[] (only the first
occurrence is useful). On 64-bit systems this avoids using more than two parsed occurrence is useful). On 64-bit systems this avoids using more than two parsed
pattern elements for items such as \3. The offset is used when an error occurs pattern elements for items such as \3. The offset is used when an error occurs

4
NON-AUTOTOOLS-BUILD
View File

@ -307,7 +307,7 @@ cache can be deleted by selecting "File > Delete Cache".
3. Create a new, empty build directory, preferably a subdirectory of the 3. Create a new, empty build directory, preferably a subdirectory of the
source dir. For example, C:\pcre2\pcre2-xx\build. source dir. For example, C:\pcre2\pcre2-xx\build.
4. Run cmake-gui from the Shell envirornment of your build tool, for example, 4. Run cmake-gui from the Shell environment of your build tool, for example,
Msys for Msys/MinGW or Visual Studio Command Prompt for VC/VC++. Do not try Msys for Msys/MinGW or Visual Studio Command Prompt for VC/VC++. Do not try
to start Cmake from the Windows Start menu, as this can lead to errors. to start Cmake from the Windows Start menu, as this can lead to errors.
@ -374,7 +374,7 @@ Otherwise:
1. Copy RunTest.bat into the directory where pcre2test.exe and pcre2grep.exe 1. Copy RunTest.bat into the directory where pcre2test.exe and pcre2grep.exe
have been created. have been created.
2. Edit RunTest.bat to indentify the full or relative location of 2. Edit RunTest.bat to identify the full or relative location of
the pcre2 source (wherein which the testdata folder resides), e.g.: the pcre2 source (wherein which the testdata folder resides), e.g.:
set srcdir=C:\pcre2\pcre2-10.00 set srcdir=C:\pcre2\pcre2-10.00

2
README
View File

@ -696,7 +696,7 @@ Test 14 contains some special UTF and UCP tests that give different output for
different code unit widths. different code unit widths.
Test 15 contains a number of tests that must not be run with JIT. They check, Test 15 contains a number of tests that must not be run with JIT. They check,
among other non-JIT things, the match-limiting features of the intepretive among other non-JIT things, the match-limiting features of the interpretive
matcher. matcher.
Test 16 is run only when JIT support is not available. It checks that an Test 16 is run only when JIT support is not available. It checks that an

2
doc/html/NON-AUTOTOOLS-BUILD.txt
View File

@ -306,7 +306,7 @@ cache can be deleted by selecting "File > Delete Cache".
3. Create a new, empty build directory, preferably a subdirectory of the 3. Create a new, empty build directory, preferably a subdirectory of the
source dir. For example, C:\pcre2\pcre2-xx\build. source dir. For example, C:\pcre2\pcre2-xx\build.
4. Run cmake-gui from the Shell envirornment of your build tool, for example, 4. Run cmake-gui from the Shell environment of your build tool, for example,
Msys for Msys/MinGW or Visual Studio Command Prompt for VC/VC++. Do not try Msys for Msys/MinGW or Visual Studio Command Prompt for VC/VC++. Do not try
to start Cmake from the Windows Start menu, as this can lead to errors. to start Cmake from the Windows Start menu, as this can lead to errors.