From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: regex.c simplification
Date: Sat, 21 Jul 2018 09:43:19 +0300 [thread overview]
Message-ID: <83h8ktytq0.fsf@gnu.org> (raw)
In-Reply-To: <51d08f86-fe0c-4eb1-8b0b-7dadb0257c02@cs.ucla.edu> (message from Paul Eggert on Fri, 20 Jul 2018 14:49:15 -0700)
> Cc: emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Fri, 20 Jul 2018 14:49:15 -0700
>
> On 07/19/2018 11:59 PM, Eli Zaretskii wrote:
> >> I was thinking of just always using the libc regexp code (whether it's
> >> GNU libc or something else).
> > Yes, that'd be a possibility. Do we have any supported platform that
> > does NOT have its own regexp code, whether in libc or as a separate
> > library?
> >
> Every POSIX-conforming platform has regexp code somewhere, using the
> POSIX API. However, I can see some trouble using that code:
>
> * Some of libc regex implementations have been reasonably buggy. Most
> GNU apps don't use these implementations any more so I'm not sure what
> their status is.
>
> * We may need to use an option like -lregex to get the system library
> implementation, and that would have to be configured.
>
> * Perhaps 'etags' users are using GNU extensions in their regular
> expressions, and if we switch to the libc API their usage will break.
We could recommend such users to install GNU regexp, which AFAIK
exposes the Posix API as well.
> * You're the expert, but as far as I know MS-Windows does not support
> the POSIX API so presumably we'd have to provide a substitute anyway,
> for MS-Windows.
GNU regexp is available as a separate library on Windows, I used it in
several ports of GNU and Unix packages.
> * etags uses the GNU API so it would have to be changed to use the POSIX
> API.
Right.
There's still the alternative which I asked about a couple of days
ago: use the Gnulib regexp without the additional code pulled in by
mbrtowc, I hope that's a viable option.
next prev parent reply other threads:[~2018-07-21 6:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 15:35 regex.c simplification Daniel Colascione
2018-06-16 15:53 ` Eli Zaretskii
2018-06-16 16:11 ` Paul Eggert
2018-06-16 16:17 ` Daniel Colascione
2018-06-16 18:06 ` Andreas Schwab
2018-06-16 19:27 ` Perry E. Metzger
2018-06-17 16:50 ` Clément Pit-Claudel
2018-06-18 14:08 ` Stefan Monnier
2018-07-17 23:58 ` Paul Eggert
2018-07-20 0:33 ` Stefan Monnier
2018-07-20 0:59 ` Paul Eggert
2018-07-20 1:42 ` Stefan Monnier
2018-07-20 6:59 ` Eli Zaretskii
2018-07-20 21:49 ` Paul Eggert
2018-07-21 6:43 ` Eli Zaretskii [this message]
2018-07-21 7:17 ` Paul Eggert
2018-08-01 0:17 ` Paul Eggert
2018-08-01 2:38 ` Brett Gilio
2018-07-20 6:58 ` Eli Zaretskii
2018-06-16 16:12 ` Daniel Colascione
2018-06-16 16:43 ` Perry E. Metzger
2018-06-16 16:09 ` Noam Postavsky
2018-06-16 16:35 ` Perry E. Metzger
2018-06-16 16:42 ` Daniel Colascione
2018-06-16 16:55 ` Eli Zaretskii
2018-06-16 18:24 ` Perry E. Metzger
2018-06-16 18:29 ` Eli Zaretskii
2018-06-16 18:58 ` Perry E. Metzger
2018-06-16 19:27 ` Eli Zaretskii
2018-06-18 9:36 ` Robert Pluim
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h8ktytq0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).