From: wmperry@aventail.com (William M. Perry)
Cc: rms@gnu.org, gsstark@mit.edu, ding@gnus.org, w3-beta@indiana.edu
Subject: Re: Regular expression performance in emacs, number of cached regexps
Date: 20 May 1998 06:47:27 -0500 [thread overview]
Message-ID: <86af8dxiy8.fsf@kramer.bp.aventail.com> (raw)
In-Reply-To: Dale Hagglund's message of "19 May 1998 23:43:02 -0700"
Dale Hagglund <rdh@best.com> writes:
> Maybe adding a new function along the lines of
>
> (re-compile REGEXP)
>
> that returns a compiled form of REGEXP would be a useful approach. Along
> with this, all the various regexp search functions could check if they're
> given a compiled or an uncompiled regexp, and either check the cache and
> compile if necessary, or just use the given compiled form.
>
> This would let authors of regexp-heavy code pre-compile their own
> regexps, avoiding the entire issue of cache size. The down-side of this
> is that over-zealous use of this could chew quite a bit of space in
> compiled regexps.
>
> Is there some reason why this sort of approach is a bad idea? I've used
> emacs extensively for many years, and written a fair amount of lisp code,
> but I'm only looked at the C internals a few times.
This is actually something that is on my todo list, but I have zero free
time right now due to my mother's illness, so its been on the back burner
for a while.
-bill p.
next prev parent reply other threads:[~1998-05-20 11:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-17 17:49 Gregory S. Stark
1998-05-17 19:20 ` Kai Grossjohann
[not found] ` <vafhg2o1z7k.fsf@ramses..cs.uni-dortmund.de>
1998-05-17 19:33 ` Hrvoje Niksic
1998-05-18 5:29 ` Richard Stallman
1998-05-18 15:49 ` William M. Perry
1998-05-19 4:45 ` Richard Stallman
1998-05-19 13:52 ` William M. Perry
1998-05-20 1:38 ` Richard Stallman
1998-05-20 6:43 ` Dale Hagglund
1998-05-20 11:47 ` William M. Perry [this message]
1998-05-21 7:13 ` Richard Stallman
1998-05-19 7:55 ` Jan Vroonhof
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=86af8dxiy8.fsf@kramer.bp.aventail.com \
--to=wmperry@aventail.com \
--cc=ding@gnus.org \
--cc=gsstark@mit.edu \
--cc=rms@gnu.org \
--cc=w3-beta@indiana.edu \
/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.
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 NNTP newsgroup(s).