From: Paul Eggert <eggert@cs.ucla.edu>
To: bug-gnulib@gnu.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: [PATCH] regex: improve comment
Date: Tue, 19 Oct 2021 01:08:19 -0700 [thread overview]
Message-ID: <20211019080819.374098-1-eggert@cs.ucla.edu> (raw)
---
lib/regexec.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/lib/regexec.c b/lib/regexec.c
index a955aa218..106f9d7ff 100644
--- a/lib/regexec.c
+++ b/lib/regexec.c
@@ -758,8 +758,7 @@ re_search_internal (const regex_t *preg, const char *string, Idx length,
offset = match_first - mctx.input.raw_mbs_idx;
}
- /* If MATCH_FIRST is out of the buffer, leave it as '\0'.
- Note that MATCH_FIRST must not be smaller than 0. */
+ /* If OFFSET is out of the buffer, leave CH as '\0'. */
ch = (mctx.input.valid_len <= offset
? 0 : re_string_byte_at (&mctx.input, offset));
if (fastmap[ch])
--
2.32.0
reply other threads:[~2021-10-19 8:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211019080819.374098-1-eggert@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bug-gnulib@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.
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).