From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: storm@cua.dk, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: regex and case-fold-search problem
Date: Thu, 29 Aug 2002 12:00:23 -0400 [thread overview]
Message-ID: <200208291600.g7TG0NZ11087@rum.cs.yale.edu> (raw)
In-Reply-To: 200208291338.WAA03607@etlken.m17n.org
> In article <5x8z2pj13t.fsf@kfs2.cua.dk>, storm@cua.dk (Kim F. Storm) writes:
> > IMO, it is wrong to handle case-fold-search for regexp ranges by
> > trying to modify the interpretation of the regex range.
>
> > Instead, the regex matcher should try to upcase and lowercase each
> > character in the string and see if either of these caracters are
> > within the given range.
>
> I also reached to that idea. It makes regexp compiling
> simpler and faster but makes regexp matching a little bit
> slower. I don't know if that slowerness is tolerable or
> not, but it's worth trying.
Two things:
- Neither `upper(lower(x)) = x' nor `lower(upper(x)) = x' are guaranteed.
- The regexp matcher right now only has access to one of the two tables
(I believe it's the `lower' but I'm not even sure) and so two chars
are deemed to match if translate(a) = translate(b).
The first might be a non-issue, I don't know.
The second is more serious because that means that if we want to use
`upper' we'll need to somehow pass that table as well, which requires
changing the interface to the reg-matching functions.
Stefan
next prev parent reply other threads:[~2002-08-29 16:00 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 6:25 regex and case-fold-search problem Kenichi Handa
2002-08-23 15:56 ` Eli Zaretskii
2002-08-24 0:51 ` Kenichi Handa
2002-08-24 1:03 ` Miles Bader
2002-08-24 9:42 ` Eli Zaretskii
2002-08-24 16:16 ` Andreas Schwab
2002-08-26 1:54 ` Miles Bader
2002-08-26 16:11 ` Stefan Monnier
2002-08-26 21:51 ` Richard Stallman
2002-08-24 9:39 ` Eli Zaretskii
2002-08-26 1:29 ` Kenichi Handa
2002-08-26 2:31 ` Miles Bader
2002-08-25 22:21 ` Kim F. Storm
2002-08-23 17:36 ` Stefan Monnier
2002-08-23 21:52 ` Stefan Monnier
2002-08-24 1:16 ` Kenichi Handa
2002-08-25 18:52 ` Stefan Monnier
2002-08-26 1:56 ` Kenichi Handa
2002-08-24 10:40 ` Kai Großjohann
2002-08-26 21:51 ` Richard Stallman
2002-08-29 8:53 ` Kenichi Handa
2002-08-29 12:33 ` Kim F. Storm
2002-08-29 13:38 ` Kenichi Handa
2002-08-29 15:00 ` Kim F. Storm
2002-08-29 16:00 ` Stefan Monnier [this message]
2002-08-30 1:11 ` Kenichi Handa
2002-08-30 19:19 ` Richard Stallman
2002-08-30 19:19 ` Richard Stallman
2002-08-30 20:08 ` Stefan Monnier
2002-09-01 13:15 ` Richard Stallman
2002-09-01 16:26 ` Stefan Monnier
2002-09-02 14:54 ` Richard Stallman
2002-09-02 16:58 ` Stefan Monnier
2002-09-04 14:13 ` Richard Stallman
2002-09-04 16:04 ` Stefan Monnier
2002-09-05 18:02 ` Richard Stallman
2002-09-06 1:00 ` re-search-forward seems to be broken Miles Bader
2002-09-06 20:03 ` Richard Stallman
2002-08-31 6:14 ` regex and case-fold-search problem Eli Zaretskii
2002-09-01 13:14 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200208291600.g7TG0NZ11087@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=storm@cua.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.