all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: Any performance comparison/guide of/for Emacs regex?
Date: Wed, 19 Jan 2011 08:27:56 +1100	[thread overview]
Message-ID: <87wrm1vr4z.fsf@puma.rapttech.com.au> (raw)
In-Reply-To: mailman.16.1295365226.21909.help-gnu-emacs@gnu.org

Oleksandr Gavenko <gavenko@bifit.com.ua> writes:

> Any performance comparison/guide of/for Emacs regex?
>
> Which construction use to get more performance?
>
>

None that I'm aware of. 

With respect to performance, just follow the golden rule and make sure
your regexp is anchored in some way. 

Many regexp implementations use a backtrackin form of regexp. If you
don't anchor your regexp in some way, the amount of work it does in
trying to find a match before giving up can grow very fast and can even
give the impression the system is locked up. 

Common anchoring techniques include using ^ and $ to anchor your regexp
to the start/end of a line and avoiding regexp with 'match everything'
type wildcards at the start and end. If you know your regexp needs to
match a specific sequence, include it and be as specific as possible.
Use the correct meta characters such as ?, *, + etc. Take advantage of
shy groups and non-greedy forms when they make sense. In general, be as
precise as you can.

Tim

-- 
tcross (at) rapttech dot com dot au


  parent reply	other threads:[~2011-01-18 21:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.16.1295365226.21909.help-gnu-emacs@gnu.org>
2011-01-18 18:29 ` Any performance comparison/guide of/for Emacs regex? Stefan Monnier
2011-01-18 21:48   ` Oleksandr Gavenko
     [not found]   ` <mailman.3.1295387371.19799.help-gnu-emacs@gnu.org>
2011-01-19  1:22     ` Stefan Monnier
2011-01-18 21:27 ` Tim X [this message]
2011-01-18 15:38 Oleksandr Gavenko
2011-01-18 15:59 ` Deniz Dogan

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=87wrm1vr4z.fsf@puma.rapttech.com.au \
    --to=timx@nospam.dev.null \
    --cc=help-gnu-emacs@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.