From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: dancol@dancol.org, emacs-devel@gnu.org,
"Perry E. Metzger" <perry@piermont.com>
Subject: Re: regex.c simplification
Date: Mon, 18 Jun 2018 11:36:33 +0200 [thread overview]
Message-ID: <87bmc8cu72.fsf@gmail.com> (raw)
In-Reply-To: <83y3fey1jy.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 16 Jun 2018 22:27:29 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Sat, 16 Jun 2018 14:58:56 -0400
>> From: "Perry E. Metzger" <perry@piermont.com>
>> Cc: dancol@dancol.org, emacs-devel@gnu.org
>>
>> The original question was "should we keep the code that isn't needed
>> by emacs on the premise something else might need it someday." I was
>> implying that, no, the odds that something else would want it someday
>> seem low.
>
> Yes, but the reason to keep the code not needed by Emacs is not
> because someone outside of Emacs will want it. It's because we
> ourselves use it in etags.
>
We could switch to external etags, and remove our copy. Iʼm assuming
there are differences between the two implementations, but I donʼt
know exactly what they are.
Robert
prev parent reply other threads:[~2018-06-18 9:36 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
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 [this message]
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=87bmc8cu72.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=dancol@dancol.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=perry@piermont.com \
/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).