unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: What’s the deal with #if _LIBC and other non-Emacs code?
Date: Tue, 26 Jul 2016 08:50:35 +0200	[thread overview]
Message-ID: <afad900e-3655-dfd2-0f82-1f9ee4d5e52d@cs.ucla.edu> (raw)
In-Reply-To: <jwvinvtyvdu.fsf-monnier+gmane.emacs.devel@gnu.org>

On 07/26/2016 04:42 AM, Stefan Monnier wrote:
> AFAIK, this code used to be in some version of glibc, but glibc has
> moved to a completely different regexp implementation many years ago.
> IIRC gnulib was the last non-Emacs package which shared this code, and
> AFAIK gnulib also dropped this (not sure if it replaced it with
> something else or what, tho).

Gnulib regularly merges as many glibc changes as it can, and is now 
using essentially the same implementation that glibc does. It should be 
fairly easy to merge the gnulib changes back into glibc, if someone 
wants to volunteer to do that.

> So, my understanding is that this code is now 100% ours with no hope to
> sync it with anyone else.

The Emacs regex code could also be merged into glibc, though that would 
be a somewhat bigger project than merging gnulib into glibc, as there 
has been little or no attempt to keep the Emacs copy in sync with glibc.




  reply	other threads:[~2016-07-26  6:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-25 22:58 What’s the deal with #if _LIBC and other non-Emacs code? Michal Nazarewicz
2016-07-26  2:34 ` Eli Zaretskii
2016-07-26  2:42   ` Stefan Monnier
2016-07-26  6:50     ` Paul Eggert [this message]
2016-07-26 14:51     ` Eli Zaretskii
2016-07-26 15:33       ` Stefan Monnier
2016-07-26 15:40         ` Eli Zaretskii
2016-07-26 16:06           ` 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=afad900e-3655-dfd2-0f82-1f9ee4d5e52d@cs.ucla.edu \
    --to=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).