The pcre2test utility needs quite a few changes to accommodate this.
It is simpler to add a new mode to it, than to make it fully
EBCDIC-native. On an ASCII system, pcre2test performs ASCII I/O, but
tranlates the input when passing it to the fully-EBCDIC-supporting
library.
Fixes#564
The previous API was not extensible to handle multi-character case rules. It required a fair bit of reworking in order to accommodate this. I had to delay the casing transformations to be done later, by buffering up the string to transform, and then allowing the callback to do an in-place transformation on the entire input to be transformed.
Add Bazel to CI using Bazelisk from the GitHub test runners.
Fix many things in the Bazel build file... and also add basic testing which executes pcre2test using RunTest.
---------
Co-authored-by: zaucy <zekewarren@gmail.com>
UCD 16 makes a lot of changes to scripts, so make sure that we have
sufficient coverage by keeping the original autogenerated tests in
addition.
Complete the code updates for changes to ScriptExtensions.txt which
is no longer sorted by script and allow for multiple unicode property
test files, depending on Unicode version.
* Correct condition for creating testout{,jit}32 directories when running Windows tests
* Enable test suites 24-26 on Windows
* ci: add dev Windows job
While at it, fix a couple of issues in RunTest.bat
---------
Co-authored-by: Carlo Marcelo Arenas Belón <carenas@gmail.com>
Still barebones and only to serve as a starting point and guideline for
how to integrate mostly non autotools environments.
Selects Intel 32-bit specifically as it is the one that has been tested
the most and also has the less number of warnings.
Test should be improved further so it is at least equivalent to what is
done in Linux, but that is orthogonal to having it integrated, and the
tests that were disabled would work locally (albeit in a newer version),
so this at least does the minimum to prevent regressions by validating
both the interpreter and JIT.
Co-authored-by: PhilipHazel <Philip.Hazel@gmail.com>
