From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: fstrcmp: Clarification regarding NOTE_ORDERED
Date: Wed, 26 Aug 2020 00:33:13 +0200 [thread overview]
Message-ID: <1976781.SQ8bVhMksu@omega> (raw)
In-Reply-To: <20200824222128.15900-1-eggert@cs.ucla.edu>
> + NOTE_ORDERED (Optional) A boolean expression saying that
> + NOTE_DELETE and NOTE_INSERT calls must be
> + issued in offset order.
This patch makes it clear that NOTE_ORDERED == false is OK in the 'fstrcmp'
module.
2020-08-25 Bruno Haible <bruno@clisp.org>
fstrcmp: Clarification regarding NOTE_ORDERED.
* lib/fstrcmp.c (NOTE_ORDERED): Define to false.
diff --git a/lib/fstrcmp.c b/lib/fstrcmp.c
index 1a4fbfd..49ce27a 100644
--- a/lib/fstrcmp.c
+++ b/lib/fstrcmp.c
@@ -46,6 +46,7 @@
ptrdiff_t edit_count;
#define NOTE_DELETE(ctxt, xoff) ctxt->edit_count++
#define NOTE_INSERT(ctxt, yoff) ctxt->edit_count++
+#define NOTE_ORDERED false
#define EARLY_ABORT(ctxt) ctxt->edit_count > 0
/* We don't need USE_HEURISTIC, since it is unlikely in typical uses of
fstrcmp(). */
prev parent reply other threads:[~2020-08-25 22:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 22:21 [PATCH] diffseq: new option NOTE_ORDERED Paul Eggert
2020-08-25 22:33 ` Bruno Haible [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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1976781.SQ8bVhMksu@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.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 read-only IMAP folder(s) and NNTP newsgroup(s).