git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 3/5] grep: add pmatch and eflags arguments to match_one_pattern()

From
René Scharfe <rene.scharfe@lsrfire.ath.cx>
Date
Mar 7, 2009, 12:30 UTC
Message-ID
<1236429027.6486.47.camel@ubuntu.ubuntu-domain>
In-Reply-To
<1236428699.6486.41.camel@ubuntu.ubuntu-domain>

Push pmatch and eflags to the callers of match_one_pattern(), which allows them to specify regex execution flags and to get the location of a match.

Since we only use the first element of the matches array and aren't interested in submatches, no provision is made for callers to provide a larger array.

eflags are ignored for fixed patterns, but that's OK, since they only have a meaning in connection with regular expressions containing ^ or $.

Signed-off-by: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
---
 grep.c |   21 ++++++++++-----------
 1 files changed, 10 insertions(+), 11 deletions(-)
diff --git a/grep.c b/grep.c
index f455182..bdcff7b 100644
--- a/grep.c
+++ b/grep.c
@@ -309,11 +309,11 @@ static struct {
 };
 
 static int match_one_pattern(struct grep_pat *p, char *bol, char *eol,
-			     enum grep_context ctx)
+			     enum grep_context ctx,
+			     regmatch_t *pmatch, int eflags)
 {
 	int hit = 0;
 	int saved_ch = 0;
-	regmatch_t pmatch[10];
 
 	if ((p->token != GREP_PATTERN) &&
 	    ((p->token == GREP_PATTERN_HEAD) != (ctx == GREP_CONTEXT_HEAD)))
@@ -332,14 +332,10 @@ static int match_one_pattern(struct grep_pat *p, char *bol, char *eol,
 	}
 
  again:
-	if (!p->fixed) {
-		regex_t *exp = &p->regexp;
-		hit = !regexec(exp, bol, ARRAY_SIZE(pmatch),
-			       pmatch, 0);
-	}
-	else {
+	if (p->fixed)
 		hit = !fixmatch(p->pattern, bol, pmatch);
-	}
+	else
+		hit = !regexec(&p->regexp, bol, 1, pmatch, eflags);
 
 	if (hit && p->word_regexp) {
 		if ((pmatch[0].rm_so < 0) ||
@@ -385,10 +381,11 @@ static int match_expr_eval(struct grep_expr *x, char *bol, char *eol,
 			   enum grep_context ctx, int collect_hits)
 {
 	int h = 0;
+	regmatch_t match;
 
 	switch (x->node) {
 	case GREP_NODE_ATOM:
-		h = match_one_pattern(x->u.atom, bol, eol, ctx);
+		h = match_one_pattern(x->u.atom, bol, eol, ctx, &match, 0);
 		break;
 	case GREP_NODE_NOT:
 		h = !match_expr_eval(x->u.unary, bol, eol, ctx, 0);
@@ -427,12 +424,14 @@ static int match_line(struct grep_opt *opt, char *bol, char *eol,
 		      enum grep_context ctx, int collect_hits)
 {
 	struct grep_pat *p;
+	regmatch_t match;
+
 	if (opt->extended)
 		return match_expr(opt, bol, eol, ctx, collect_hits);
 
 	/* we do not call with collect_hits without being extended */
 	for (p = opt->pattern_list; p; p = p->next) {
-		if (match_one_pattern(p, bol, eol, ctx))
+		if (match_one_pattern(p, bol, eol, ctx, &match, 0))
 			return 1;
 	}
 	return 0;
-- 
1.6.2
Previous: René ScharfeNext: René Scharfe
Message 4 of 10 in “grep: color search patterns”
  1. 0/5 grep: color search patternsRené Scharfe, Mar 7, 2009
  2. 1/5 grep: micro-optimize hit collection for AND nodesRené Scharfe, Mar 7, 2009
  3. 2/5 grep: remove grep_opt argument from match_expr_eval()René Scharfe, Mar 7, 2009
  4. 3/5 grep: add pmatch and eflags arguments to match_one_pattern()René Scharfe, Mar 7, 2009
  5. 4/5 grep: color patterns in outputRené Scharfe, Mar 7, 2009
  6. 5/5 grep: add support for coloring with external grepsRené Scharfe, Mar 7, 2009
  7. Nguyen Thai Ngoc DuyMar 10, 2009
  8. René ScharfeMar 10, 2009
  9. grep: prefer builtin over external one when coloring resultspclouds@gmail.com, Mar 16, 2009
  10. René ScharfeMar 16, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.