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

[PATCH v6 04/11] ref-filter: introduce parsing functions for each valid atom

From
Karthik Nayak <karthik.188@gmail.com>
Date
Feb 17, 2016, 18:06 UTC
Message-ID
<1455732379-22479-5-git-send-email-Karthik.188@gmail.com>
In-Reply-To
<1455732379-22479-1-git-send-email-Karthik.188@gmail.com>

Parsing atoms is done in populate_value(), this is repetitive and hence expensive. Introduce a parsing function which would let us parse atoms beforehand and store the required details into the 'used_atom' structure for further usage.

Helped-by: Eric Sunshine <sunshine@sunshineco.com>
Helped-by: Ramsay Jones <ramsay@ramsayjones.plus.com>
Helped-by: Andreas Schwab <schwab@linux-m68k.org>
Signed-off-by: Karthik Nayak <Karthik.188@gmail.com>
---
 ref-filter.c | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/ref-filter.c b/ref-filter.c
index 8139709..8a34ba1 100644
--- a/ref-filter.c
+++ b/ref-filter.c
@@ -36,6 +36,7 @@ static int need_color_reset_at_eol;
 static struct {
 	const char *name;
 	cmp_type cmp_type;
+	void (*parser)(struct used_atom *atom, const char *arg);
 } valid_atom[] = {
 	{ "refname" },
 	{ "objecttype" },
@@ -114,6 +115,7 @@ struct atom_value {
 int parse_ref_filter_atom(const char *atom, const char *ep)
 {
 	const char *sp;
+	const char *arg;
 	int i, at;
 
 	sp = atom;
@@ -132,16 +134,16 @@ int parse_ref_filter_atom(const char *atom, const char *ep)
 	/* Is the atom a valid one? */
 	for (i = 0; i < ARRAY_SIZE(valid_atom); i++) {
 		int len = strlen(valid_atom[i].name);
+
 		/*
 		 * If the atom name has a colon, strip it and everything after
 		 * it off - it specifies the format for this entry, and
 		 * shouldn't be used for checking against the valid_atom
 		 * table.
 		 */
-		const char *formatp = strchr(sp, ':');
-		if (!formatp || ep < formatp)
-			formatp = ep;
-		if (len == formatp - sp && !memcmp(valid_atom[i].name, sp, len))
+		arg = memchr(sp, ':', ep - sp);
+		if (len == (arg ? arg : ep) - sp &&
+		    !memcmp(valid_atom[i].name, sp, len))
 			break;
 	}
 
@@ -154,6 +156,10 @@ int parse_ref_filter_atom(const char *atom, const char *ep)
 	REALLOC_ARRAY(used_atom, used_atom_cnt);
 	used_atom[at].name = xmemdupz(atom, ep - atom);
 	used_atom[at].type = valid_atom[i].cmp_type;
+	if (arg)
+		arg = used_atom[at].name + (arg - atom) + 1;
+	if (valid_atom[i].parser)
+		valid_atom[i].parser(&used_atom[at], arg);
 	if (*atom == '*')
 		need_tagged = 1;
 	if (!strcmp(used_atom[at].name, "symref"))
-- 
2.7.1
Previous: Karthik NayakNext: Karthik Nayak
Message 11 of 18 in “ref-filter: use parsing functions”
  1. 00/11 ref-filter: use parsing functionsKarthik Nayak, Feb 17, 2016
  2. 01/11 ref-filter: use string_list_split over strbuf_splitKarthik Nayak, Feb 17, 2016
  3. Eric SunshineFeb 17, 2016
  4. Jeff KingFeb 17, 2016
  5. Junio C HamanoFeb 17, 2016
  6. Eric SunshineFeb 17, 2016
  7. Jeff KingFeb 17, 2016
  8. Karthik NayakFeb 18, 2016
  9. 02/11 ref-filter: bump 'used_atom' and related code to the topKarthik Nayak, Feb 17, 2016
  10. 03/11 ref-filter: introduce struct used_atomKarthik Nayak, Feb 17, 2016
  11. 04/11 ref-filter: introduce parsing functions for each valid atomKarthik Nayak, Feb 17, 2016
  12. 05/11 ref-filter: introduce color_atom_parser()Karthik Nayak, Feb 17, 2016
  13. 06/11 ref-filter: introduce parse_align_position()Karthik Nayak, Feb 17, 2016
  14. 07/11 ref-filter: introduce align_atom_parser()Karthik Nayak, Feb 17, 2016
  15. 08/11 ref-filter: align: introduce long-form syntaxKarthik Nayak, Feb 17, 2016
  16. 09/11 ref-filter: introduce remote_ref_atom_parser()Karthik Nayak, Feb 17, 2016
  17. 10/11 ref-filter: introduce contents_atom_parser()Karthik Nayak, Feb 17, 2016
  18. 11/11 ref-filter: introduce objectname_atom_parser()Karthik Nayak, Feb 17, 2016

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.