Branch: refs/heads/blead
Home: https://github.com/Perl/perl5
Commit: c8820453795c65eb735d12db8fde5013b2b081be
https://github.com/Perl/perl5/commit/c8820453795c65eb735d12db8fde5013b2b081be
Author: Karl Williamson <k...@cpan.org>
Date: 2023-07-24 (Mon, 24 Jul 2023)
Changed paths:
M t/loc_tools.pl
Log Message:
-----------
loc_tools: Slight refactor of try_locale() loop
This eliminates a conditional in the loop, and makes sure the category
that is supposed to be tried first actually is, and isn't tried again in
a future iteration.
Commit: 5077456c5df9ed5b320932bea29a05b2a15c3028
https://github.com/Perl/perl5/commit/5077456c5df9ed5b320932bea29a05b2a15c3028
Author: Karl Williamson <k...@cpan.org>
Date: 2023-07-24 (Mon, 24 Jul 2023)
Changed paths:
M t/loc_tools.pl
Log Message:
-----------
loc_tools: Change variable name
This is in preparation for a future commit
Commit: 80e09067dd552092736043643df16ad52135f66c
https://github.com/Perl/perl5/commit/80e09067dd552092736043643df16ad52135f66c
Author: Karl Williamson <k...@cpan.org>
Date: 2023-07-24 (Mon, 24 Jul 2023)
Changed paths:
M t/loc_tools.pl
Log Message:
-----------
loc_tools: Avoid some problematic cases
Some platforms have exhibited problematic behavior when setting one
category to a locale, but setting another category to that same
locale yields a differently named locale. This might be a synonym, but
we don't know, and if it is a synonym, why the variance in results?
And if we use that locale anyway, there have been weird results.
Therefore, skip it. But this can legally happen without bad results
(because locale.c knows and handles this situation specially) when the
two locale names are POSIX and C, so accept those.
Compare: https://github.com/Perl/perl5/compare/30fdb5757ad4...80e09067dd55
