unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Perry E. Metzger" <perry@piermont.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Daniel Colascione <dancol@dancol.org>, emacs-devel@gnu.org
Subject: Re: regex.c simplification
Date: Sat, 16 Jun 2018 14:24:02 -0400	[thread overview]
Message-ID: <20180616142402.6a1bdb08@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <834li2zn5d.fsf@gnu.org>

On Sat, 16 Jun 2018 19:55:42 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Sat, 16 Jun 2018 09:42:37 -0700
> > From: "Daniel Colascione" <dancol@dancol.org>
> > Cc: Daniel Colascione <dancol@dancol.org>, emacs-devel@gnu.org
> >   
> > > The emacs regex code is hardly state of the art. I would
> > > suggest that there are many other, better, free software
> > > implementations of regexes.  
> > 
> > There are. Unfortunately, none of them understand predicates like
> > \= and \s|.  
> 
> Right.  And there are a few more features important to Emacs that
> other implementations don't support.
> 
> So, while I think modernizing our regex code would be a welcome
> development, we shouldn't mislead ourselves into thinking that any
> other implementation could be a drop-in replacement.  Some work will
> be needed to add the features we expect.
> 

I was arguing in the opposite direction, that there isn't much point
in thinking others will be interested in using the Emacs regex code
in the future.

-- 
Perry E. Metzger		perry@piermont.com



  reply	other threads:[~2018-06-16 18:24 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
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 [this message]
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=20180616142402.6a1bdb08@jabberwock.cb.piermont.com \
    --to=perry@piermont.com \
    --cc=dancol@dancol.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).