[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: fstrcmp: Clarification regarding NOTE_ORDERED
From: |
Bruno Haible |
Subject: |
Re: fstrcmp: Clarification regarding NOTE_ORDERED |
Date: |
Wed, 26 Aug 2020 00:33:13 +0200 |
User-agent: |
KMail/5.1.3 (Linux/4.4.0-186-generic; KDE/5.18.0; x86_64; ; ) |
> + 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(). */