From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Clément Pit--Claudel" <clement.pit@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Regular expression libraries
Date: Fri, 16 Dec 2016 16:42:00 +0100 [thread overview]
Message-ID: <m3inqjyj7b.fsf@gnus.org> (raw)
In-Reply-To: <aff5a8a0-7055-b6ad-6ef3-2a44aa0d94a6@gmail.com> ("Clément Pit--Claudel"'s message of "Fri, 16 Dec 2016 09:54:35 -0500")
Clément Pit--Claudel <clement.pit@gmail.com> writes:
> Wait, now I'm confused. The master branch of glibc *does* include the following in regex.h:
>
> extern int __re_search_2
> (struct re_pattern_buffer *buffer, const char *string1,
> int length1, const char *string2, int length2,
> int start, int range, struct re_registers *regs, int stop);
>
> … but the implementation just allocates a large buffer and concatenates both strings?
Yes. If I remember correctly, a glibc developer popped up here a couple
of years ago announcing that they were going to do that change (thereby
making __re_search_2 incredibly slow, but retained for compatibility).
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-12-16 15:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 19:00 Regular expression libraries Clément Pit--Claudel
2016-12-15 20:10 ` Eli Zaretskii
2016-12-15 20:30 ` Paul Eggert
2016-12-15 22:00 ` Andreas Schwab
2016-12-16 7:20 ` Paul Eggert
2016-12-16 14:31 ` Clément Pit--Claudel
2016-12-16 14:54 ` Clément Pit--Claudel
2016-12-16 15:42 ` Lars Ingebrigtsen [this message]
2016-12-16 20:06 ` Clément Pit--Claudel
2016-12-16 21:25 ` Eli Zaretskii
2016-12-16 17:43 ` Paul Eggert
2016-12-15 22:16 ` Clément Pit--Claudel
2016-12-16 5:15 ` Stefan Monnier
2016-12-16 14:41 ` Clément Pit--Claudel
2016-12-16 17:45 ` Paul Eggert
2016-12-16 20:07 ` Clément Pit--Claudel
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3inqjyj7b.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=clement.pit@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.