Re: [PATCH v4 1/4] i18n: factorize more 'incompatible options' messages

From: Johannes Sixt <j6t@kdbg.org>
Date: Feb 2, 2022, 17:29 UTC
Message-ID: <bc8fb1ae-4ad0-b435-758c-d5ecc12ffe25@kdbg.org>
In-Reply-To: <29731fdd-ca0c-a3f6-84c7-7429ccef5673@gmail.com>

Am 02.02.22 um 17:05 schrieb Jean-Noël Avila:

> With "static", we ensure that either it is inlined or there is a static
> function (in which case, this bit of code will be duplicated across
> compilation units).

That is the plan. Since the function is declared static, the compiler has much more freedom to inline it because it knows that the function is inaccessible outside the current compilation unit.

Besides, if you grep for 'inline', you will only find 'static inline' (except in some borrowed code). static inline it is, or you pick the macro or out-of-line solution.

-- Hannes

$ 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.