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

Re: xmemdup patches

From
Pierre Habouzit <madcoder@debian.org>
Date
Sep 17, 2007, 16:14 UTC
Message-ID
<20070917161420.GC460@artemis.corp>
In-Reply-To
<20070917161113.GB460@artemis.corp>
On lun, sep 17, 2007 at 04:11:13 +0000, Pierre Habouzit wrote:
>   There were 41 of those places.
  I forgot to say, I replaced _some_ xstrndup uses with a xmemdup when
it was clear to me that xmemdup was Okay. I left some alone when it
wasn't obvious in the first 10 seconds that xmemdup would work the same
way.
  The real goal is code brevity and readability, xstrndup or xmemdup are
the same in that regard, and I don't think the small performance gain is
really worth the headache.
-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org
Previous: Pierre HabouzitNext: Johannes Schindelin
Message 6 of 8 in “xmemdup patches”
  1. Pierre HabouzitSep 17, 2007
  2. 1/2 Add xmemdup that duplicates a block of memory, and NUL terminates it.Pierre Habouzit, Sep 15, 2007
  3. 2/2 Use xmemdup in many places.Pierre Habouzit, Sep 15, 2007
  4. Junio C HamanoSep 19, 2007
  5. Pierre HabouzitSep 19, 2007
  6. Pierre HabouzitSep 17, 2007
  7. Johannes SchindelinSep 17, 2007
  8. Pierre HabouzitSep 17, 2007

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.