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

Re: [PATCH/RFC v1 0/5] add strbuf_set operations

From
Duy Nguyen <pclouds@gmail.com>
Date
Jun 9, 2014, 10:39 UTC
Message-ID
<CACsJy8D_eM9OtH=6Z_F0P7GZpqmAdSCEnBjCr_gniZr649P1uw@mail.gmail.com>
In-Reply-To
<cover.1402301815.git.jmmahler@gmail.com>
On Mon, Jun 9, 2014 at 3:36 PM, Jeremiah Mahler <jmmahler@gmail.com> wrote:
Show 12 quoted lines
> Currently, the data in a strbuf is modified using add operations.  To
> set the buffer to some data a reset must be performed before an add.
>
>   strbuf_reset(buf);
>   strbuf_add(buf, cb.buf.buf, cb.buf.len);
>
> And this is a common sequence of operations with 70 occurrences found in
> the current source code.  This includes all the different variations
> (add, addf, addstr, addbuf, addch).
>
>   FILES=`find ./ -name '*.c'`
>   CNT=$(pcregrep -M "strbuf_reset.*\n.*strbuf_add" $FILES | wc -l)

Hmm.. I wonder if git-grep could do this.. There's pcre support but I never tried.

>   CNT=$(echo "$CNT / 2" | bc)
>   echo $CNT
>   70

The change in this series looks nice. There's another pattern, save strbuf length, then strbuf_setlen() at the beginning or the end of a loop. But I think it's less often.

-- 
Duy
Previous: Jeremiah MahlerNext: Jeremiah Mahler
Message 11 of 12 in “add strbuf_set operations”
  1. 0/5 add strbuf_set operationsJeremiah Mahler, Jun 9, 2014
  2. 1/5 add strbuf_set operationsJeremiah Mahler, Jun 9, 2014
  3. 2/5 add strbuf_set operations documentationJeremiah Mahler, Jun 9, 2014
  4. Eric SunshineJun 9, 2014
  5. Jeremiah MahlerJun 9, 2014
  6. 3/5 sha1_name.c: cleanup using strbuf_set operationsJeremiah Mahler, Jun 9, 2014
  7. 4/5 fast-import.c: cleanup using strbuf_set operationsJeremiah Mahler, Jun 9, 2014
  8. Eric SunshineJun 9, 2014
  9. Jeremiah MahlerJun 9, 2014
  10. 5/5 builtin/remote.c: cleanup using strbuf_set operationsJeremiah Mahler, Jun 9, 2014
  11. Duy NguyenJun 9, 2014
  12. Jeremiah MahlerJun 9, 2014

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.