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

Re: [PATCH v3] CodingGuidelines: discourage arbitrary suffixes in function names

From
Taylor Blau <me@ttaylorr.com>
Date
Oct 24, 2024, 16:50 UTC
Message-ID
<Zxp67zpIsxAe15gN@nand.local>
In-Reply-To
<20241024105357.2605168-1-karthik.188@gmail.com>
On Thu, Oct 24, 2024 at 12:53:57PM +0200, Karthik Nayak wrote:
Show 7 quoted lines
> We often name functions with arbitrary suffixes like `_1` as an
> extension of another existing function. This creates confusion and
> doesn't provide good clarity into the functions purpose. Let's document
> good function naming etiquette in our CodingGuidelines.
>
> Signed-off-by: Karthik Nayak <karthik.188@gmail.com>
> ---

Thanks, I think that this version is looking quite good. Let's let it simmer a little longer so folks can continue to discuss, but I think that this is looking quite good.

Thanks, Taylor

Previous: karthik nayak
Message 3 of 3 in “CodingGuidelines: discourage arbitrary suffixes in function names”
  1. CodingGuidelines: discourage arbitrary suffixes in function namesKarthik Nayak, Oct 24, 2024
  2. karthik nayakOct 24, 2024
  3. Taylor BlauOct 24, 2024

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.