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

Re: [PATCH ps/stash-in-c] strbuf_vinsertf: provide the correct buffer size to vsnprintf

From
Johannes Sixt <j6t@kdbg.org>
Date
Feb 6, 2019, 18:11 UTC
Message-ID
<f02e73e6-7e0e-6cd9-3d3a-b2b74d03f6be@kdbg.org>
In-Reply-To
<nycvar.QRO.7.76.6.1902061242380.41@tvgsbejvaqbjf.bet>
Am 06.02.19 um 12:56 schrieb Johannes Schindelin:
Show 14 quoted lines
> On Tue, 5 Feb 2019, Johannes Sixt wrote:
>> Am 05.02.19 um 12:06 schrieb Johannes Schindelin:
>>> The real examples are much more mundane, and very different from what you
>>> suspected, e.g. inserting the tag header before the tag message in
>>> `create_tag()` in `builtin/tag.c`. Basically, it is building up a strbuf
>>> for the sake of calling `strbuf_insert()` to insert that string elsewhere.
>>
>> I had a look, and this example does not convince me at all. If
>> separation of concerns were applied well around the launch_editor APIs,
>> you would not need strbuf_insert() in the first place. But, alas, these
>> functions focus more on DRY, and that is often the opposite of
>> separation of concerns.
> 
> So you actually are convinced that it is needed in this instance. Good.
I thought I said quite the opposite.

But never mind. Since I'm not going to help refactor any C code anyway as long as the result is still C code, who am I to complain about the existence of strbuf_vinsertf()?

-- Hannes
Previous: Johannes Schindelin
Message 13 of 13 in “strbuf_vinsertf: provide the correct buffer size to vsnprintf”
  1. strbuf_vinsertf: provide the correct buffer size to vsnprintfJohannes Sixt, Feb 3, 2019
  2. Johannes SixtFeb 4, 2019
  3. Johannes SchindelinFeb 4, 2019
  4. Johannes SixtFeb 4, 2019
  5. Johannes SchindelinFeb 5, 2019
  6. Johannes SchindelinFeb 4, 2019
  7. Junio C HamanoFeb 4, 2019
  8. Johannes SchindelinFeb 5, 2019
  9. Junio C HamanoFeb 5, 2019
  10. Johannes SchindelinFeb 6, 2019
  11. Johannes SixtFeb 5, 2019
  12. Johannes SchindelinFeb 6, 2019
  13. Johannes SixtFeb 6, 2019

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.