unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Miles Bader <miles@gnu.org>
Cc: "Lennart Borgman \(gmail\)" <lennart.borgman@gmail.com>,
	Emacs Devel <emacs-devel@gnu.org>
Subject: Re: What is the difference between looking-at and an anchored search?
Date: Thu, 17 Jul 2008 14:33:33 +0200	[thread overview]
Message-ID: <86vdz43d2a.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <buo7ibku2ky.fsf@dhapc248.dev.necel.com> (Miles Bader's message of "Thu, 17 Jul 2008 21:17:49 +0900")

Miles Bader <miles.bader@necel.com> writes:

> "Lennart Borgman (gmail)" <lennart.borgman@gmail.com> writes:
>> looking-at does not have a BOUND parameter, but re-search-forward
>> have. This makes re-search-forward a bit more flexible.
>>
>> I am looking at some code where I would have use for that flexibility,
>> but I wonder if there is any drawback with replacing looking-at with
>> re-search-forward (with an achored pattern).
>>
>> Is there any? Performance?
>
> If you want to reject matches that extend past some point, just do
> something like:
>
>    (and (looking-at REGEXP) (<= (match-end 0) BOUND))

That is not the same.

(with-temp-buffer (insert "abc")
  (goto-char 1)
  (list
    (re-search-forward ".*" 2)
    (progn (goto-char 1)
      (and (looking-at ".*") (<= (match-end 0) 2)))))

=> (2 nil)

-- 
David Kastrup




      parent reply	other threads:[~2008-07-17 12:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17 11:14 What is the difference between looking-at and an anchored search? Lennart Borgman (gmail)
2008-07-17 12:17 ` Miles Bader
2008-07-17 12:21   ` Lennart Borgman
2008-07-17 12:29     ` Johan Bockgård
2008-07-17 17:45       ` Lennart Borgman (gmail)
2008-07-17 12:35     ` Miles Bader
2008-07-17 12:42       ` Lennart Borgman
2008-07-17 12:52         ` Miles Bader
2008-07-17 14:17           ` Lennart Borgman
2008-07-17 12:33   ` David Kastrup [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=86vdz43d2a.fsf@lola.quinscape.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman@gmail.com \
    --cc=miles@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 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).