unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dima Kogan <lists@dima.secretsauce.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Embedded modifiers in the regex engine
Date: Sat, 27 Feb 2016 17:50:01 -0800	[thread overview]
Message-ID: <87wpppioxi.fsf@secretsauce.net> (raw)
In-Reply-To: <83mvqnet3t.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Dima Kogan <dima@secretsauce.net>
>> Date: Thu, 25 Feb 2016 23:19:32 -0800
>> CC: emacs-devel@gnu.org
>> 
>> I'm looking at importing the regex test suite in glibc to emacs.
>> Would this be possible even if the copyright holders of those tests
>> haven't assigned their work to the fsf? These are tests and not part
>> of emacs on some level, so would that make it ok?
>
> If the test suite is GPL v3+, I don't think there should be a
> problem

If only. Some of the test cases in glibc are their own (LGPL) and some
others came from other projects (boost, BSD, MIT). To be clear, I'm
talking about the test cases themselves, not the code that evaluates the
tests. Does this mean we need to write our own test if we want them?

I did write an evaluator for one of the set of tests. It told me that
the emacs regexen don't support the [.xxx.] and [=xxx=] constructs,
which we already know. It also told me that the glibc regex engine
throws an error when you give it an invalid range, such as [b-a], but
emacs silently matches nothing. I think this is a bug, but probably not
one that's worth fixing on its own.

From the earlier emails it wasn't obvious if there was already a
long-term plan to replace the regex engine. Is there such a plan? What
do we hope to move to?

Thanks!



  reply	other threads:[~2016-02-28  1:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25  1:32 Embedded modifiers in the regex engine Dima Kogan
2016-02-25  6:11 ` John Wiegley
2016-02-25 21:05   ` Stefan Monnier
2016-02-25 16:15 ` Eli Zaretskii
2016-02-26  7:19   ` Dima Kogan
2016-02-26  9:08     ` Eli Zaretskii
2016-02-28  1:50       ` Dima Kogan [this message]
2016-02-28 16:00         ` Eli Zaretskii
2016-02-29 13:30           ` Richard Stallman
2016-03-01  0:49             ` Aurélien Aptel
2016-03-01 16:55               ` Richard Stallman
2016-03-09  0:34                 ` Dima Kogan
2016-03-28  0:23                   ` Dima Kogan
2016-03-28 15:28                     ` Eli Zaretskii
2016-03-28 18:05                       ` Dima Kogan
2016-03-28 18:24                         ` Eli Zaretskii
2016-03-29 21:23                           ` Dima Kogan
2016-03-31 16:28                             ` Eli Zaretskii
2016-04-23  4:17                             ` Dima Kogan
2016-04-23  7:48                               ` Eli Zaretskii
2016-04-24  7:34                                 ` Dima Kogan
2016-03-28 16:09                     ` Stefan Monnier

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=87wpppioxi.fsf@secretsauce.net \
    --to=lists@dima.secretsauce.net \
    --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).