Front page | perl.perl5.porters |
Postings from February 2018
Re: [perl.git] branch blead updated. v5.27.8-353-g4b262b1674
Thread Previous
From:
Sawyer X
Date:
February 26, 2018 10:55
Subject:
Re: [perl.git] branch blead updated. v5.27.8-353-g4b262b1674
Message ID:
4119949e-cc7d-80e6-dba5-a96d954d4a0c@gmail.com
On 02/25/2018 10:45 PM, Karl Williamson wrote:
> On 02/25/2018 08:57 AM, H.Merijn Brand wrote:
>> On Sun, 25 Feb 2018 09:29:02 -0600, "Craig A. Berry"
>> <craigberry@mac.com> wrote:
>>
>>> On Feb 25, 2018, at 7:12 AM, H.Merijn Brand <h.m.brand@xs4all.nl>
>>> wrote:
>>>>
>>>> On Sat, 24 Feb 2018 08:59:57 -0600, "Craig A. Berry"
>>>> <craigberry@mac.com> wrote:
>>>>
>>>>> On 2/20/18 4:55 AM, H.Merijn Brand wrote:
>>>>>> In perl.git, the branch blead has been updated
>>>>>>
>>>>>> <https://perl5.git.perl.org/perl.git/commitdiff/4b262b167490219129b4e3f8e3f6403a31ed95d2?hp=4eaf16e87417b79e64c5b779686914dc86b86520>
>>>>>>
>>>>>>
>>>>>> - Log
>>>>>> -----------------------------------------------------------------
>>>>>> commit 4b262b167490219129b4e3f8e3f6403a31ed95d2
>>>>>> Author: H.Merijn Brand <h.m.brand@xs4all.nl>
>>>>>> Date: Tue Feb 20 11:55:17 2018 +0100
>>>>>>
>>>>>> Move note about defective locale on HP-UX to README.hpux
>>>>
>>>> @Karl, I just *moved* the remarks from hints to README, just slightly
>>>> altered the text to better fit a README. Did I interpret the original
>>>> comment incorrectly?
>>>
>>> You reversed its meaning by changing "this locale doesn't think" to
>>> "this locale thinks."
>>
>> Fixed and pushed
>>
>>>>>> -----------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>> Summary of changes:
>>>>>> README.hpux | 9 +++++++++
>>>>>> hints/hpux.sh | 5 -----
>>>>>> 2 files changed, 9 insertions(+), 5 deletions(-)
>>>>>>
>>>>>> diff --git a/README.hpux b/README.hpux
>>>>>> index e1857e08dc..3bd4be3e3d 100644
>>>>>> --- a/README.hpux
>>>>>> +++ b/README.hpux
>>>>>> @@ -563,6 +563,15 @@ questions about 64-bit numbers when
>>>>>> Configure asks you, you may get a configuration that cannot be
>>>>>> compiled, or that does not function as expected.
>>>>>>
>>>>>> +=head2 Locales on HP-UX
>>>>>> +
>>>>>> +HP-UX installs the locale C<univ.utf8> on all systems. Up to and
>>>>>> +including HP-UX 11.23, this local is defective in that it thinks
>>>>>> that +the characters C<< $ + < = > ^ ` | >> and C<~> are
>>>>>> punctuation, which +they are not according to the Unicode
>>>>>> standards.
>>>>>
>>>>> I think you said this backwards and reversed "doesn't think" in
>>>>> the hints to "thinks". These characters are members of the punct
>>>>> class according to POSIX:
>>>>>
>>>>> <http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap07.html#tag_07_03_01_01>
>>>>>
>>>>>
>>>>> It's confusing because the author(s) of the standard decided to
>>>>> use the word "punctuation" to describe things that are definitely
>>>>> not punctuation, apparently not knowing that characters such as
>>>>> mathematical symbols and currency symbols are not punctuation. As
>>>>> a result, ispunct() is useless for identifying punctuation and
>>>>> really just identifies printable characters that are not letters,
>>>>> numbers, or space.
>>>>>
>>>>> I guess the only notable thing for Perl is that it complies with
>>>>> the current standard even where the C library uses an older and
>>>>> correct but non-standard definition.
>>>>
>>>> I can make it direction-neutral as in
>>>>
>>>> HP-UX installs the locale C<univ.utf8> on all systems. Up to and
>>>> including HP-UX 11.23, this local is defective in that it disagrees
>>>> with Unicode on the characters C<< $ + < = > ^ ` | >> and C<~> being
>>>> punctuation or not, which they are not according to the Unicode
>>>> standards.
>>>
>>> These *are* punctuation according to POSIX (and apparently Unicode).
>>>
>>>> @Karl, is en_US.utf8 similarly affected?
>>>> https://smoke.procura.nl/hpux1123/511/cc/mktest.rpt
>>>>
>>>> If so, should those tests be skipped om all HP-UX <= 11.23 ?
>>>
>>> I believe Karl plans to remove the warning as it causes trouble on
>>> AIX and VMS as well. The smoke-me/khw-locale branch no longer has
>>> those troubles. To me it would make sense to document somewhere that
>>> Perl uses its own standards-compliant character classes even when the
>>> local C library doesn't comply with the current standard,
>>
>> 👍 +1
>>
>>> but giving users a run-time warning that they can't do anything about
>>> seems harsh.
>
> I already was in the process of updating perldiag, but I can't push
> until we have a perldelta suitable for 5.27.10.
Hopefully resolved today.
Thread Previous