Branch: refs/heads/blead
Home: https://github.com/Perl/perl5
Commit: 8c05864e82c73bc9d981f3514a0d245431b6b8f1
https://github.com/Perl/perl5/commit/8c05864e82c73bc9d981f3514a0d245431b6b8f1
Author: Karl Williamson <k...@cpan.org>
Date: 2025-05-15 (Thu, 15 May 2025)
Changed paths:
M t/uni/method.t
Log Message:
-----------
uni/method.t: Update, and don't test specific garbage
The modern way to change UTF-8 to its component bytes is to use
utf8::encode
Some of the tests are making sure that those component bytes aren't
mistaken for being UTF-8. What those component bytes are is not
actually relevant, but the tests were looking at the specific expected
values of them. The problem is that these differ on EBCDIC vs ASCII
platforms. Several commits had been added to try to get the correct
values on both types, but EBCDIC still was getting failures. And, there
is no need to test for the specific values of these irrelevant bytes.
What is important is that they were not misinterpreted as if they were
UTF-8.
This commit goes back to the original tests before those other commits
were added, and changes the matching pattern to not look for the
specific irrelevant byte values.
Doing so makes the tests pass on both types of platforms.
Commit: bb057f76a00e8a72d81a6731415f1692a1040a5e
https://github.com/Perl/perl5/commit/bb057f76a00e8a72d81a6731415f1692a1040a5e
Author: Karl Williamson <k...@cpan.org>
Date: 2025-05-15 (Thu, 15 May 2025)
Changed paths:
M t/uni/method.t
Log Message:
-----------
uni/method.t: White-space only
Some test descriptions were split over input lines, leading to ragged
output (suppressed under harness testing).
Compare: https://github.com/Perl/perl5/compare/49ca1008a284...bb057f76a00e
To unsubscribe from these emails, change your notification settings at
https://github.com/Perl/perl5/settings/notifications
