[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#3687: 23.1.50; inconsistency in multibyte eight-bit regexps [PATCH]
From: |
Eli Zaretskii |
Subject: |
bug#3687: 23.1.50; inconsistency in multibyte eight-bit regexps [PATCH] |
Date: |
Fri, 28 Jun 2019 19:20:13 +0300 |
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Fri, 28 Jun 2019 17:00:33 +0200
> Cc: mituharu@math.s.chiba-u.ac.jp, monnier@iro.umontreal.ca,
> 3687@debbugs.gnu.org
>
> 28 juni 2019 kl. 16.40 skrev Eli Zaretskii <eliz@gnu.org>:
> >
> > So this means \240 is no longer the same as NBSP and \300 is no longer
> > the same as À? But \176 is still the same as ~?
>
> This has been the case for quite a while; the patch does not change any of
> this.
>
> > So you are saying that we will consider the raw bytes as if they
> > followed ASCII characters in the lexicographical order? But non-ASCII
> > characters whose codepoints start at 0x80? where are they in this
> > order?
>
> Again, this is existing semantics and the patch does not change any of it.
>
> It sounds like you misunderstand the patch, which means that I have been bad
> at explaining it. It just fixes a few edge cases related to raw bytes in
> regexp matching. It does not attempt to change existing semantics, other than
> where they are clearly buggy, such as "\x9f" and "[\x9f]" not being
> equivalent regexps.
Maybe I did misunderstand: if the patch change nothing fundamental,
then why did you need to precede it with "principles"?
But since you already pushed the change, I guess there's no reason to
discuss this, and I regret I replied.