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

Re: C internals cleanup

From
Andy Lester <andy@petdance.com>
Date
Apr 13, 2009, 04:29 UTC
Message-ID
<A60582E3-0374-4922-B6C9-42BCF2DCAFFB@petdance.com>
In-Reply-To
<7v4owtw623.fsf@gitster.siamese.dyndns.org>
> The general rule of thumb is to do such a clean-up before you start to
> work on something of substance.
I guess that's all in how one defines "substance." :-)

My ultimate goal is to get more stringent error-checking, to get more compiler warnings enabled, and to get a splint target. splint is fantastic for tracking all sorts of memory and logic problems, but benefits greatly from getting the const qualifiers in place. Even gcc will be happier.

Thanks for the recap. It's hard to absorb what you just described just from reading mailing list history.

xoa

-- Andy Lester => andy@petdance.com => www.petdance.com => AIM:petdance

Previous: Junio C Hamano
Message 3 of 3 in “C internals cleanup”
  1. Andy LesterApr 13, 2009
  2. Junio C HamanoApr 13, 2009
  3. Andy LesterApr 13, 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.