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

Re: /* compiler workaround */ - what was the issue?

From
Marc Branchaud <marcnarc@xiplink.com>
Date
May 6, 2016, 19:30 UTC
Message-ID
<572CF0D5.6010305@xiplink.com>
In-Reply-To
<xmqq60ur3tlu.fsf@gitster.mtv.corp.google.com>
On 2016-05-06 02:54 PM, Junio C Hamano wrote:
Show 5 quoted lines
>
> I wonder if can we come up with a short and sweet notation to remind
> futhre readers that this "initialization" is not initializing but
> merely squelching warnings from stupid compilers, and agree to use
> it consistently?
Perhaps
	#define COMPILER_UNINITIALIZED_WARNING_INITIALIZER 0
or, for short-and-sweet
	#define CUWI 0
?
:)
		M.
Previous: Junio C HamanoNext: Junio C Hamano
Message 8 of 15 in “/* compiler workaround */ - what was the issue?”
  1. Philip OakleyMay 5, 2016
  2. Junio C HamanoMay 5, 2016
  3. Duy NguyenMay 6, 2016
  4. Philip OakleyMay 6, 2016
  5. Ramsay JonesMay 6, 2016
  6. Philip OakleyMay 6, 2016
  7. Junio C HamanoMay 6, 2016
  8. Marc BranchaudMay 6, 2016
  9. Junio C HamanoMay 6, 2016
  10. Stefan BellerMay 6, 2016
  11. Philip OakleyMay 9, 2016
  12. Randall S. BeckerMay 9, 2016
  13. Marc BranchaudMay 6, 2016
  14. Ramsay JonesMay 6, 2016
  15. Ramsay JonesMay 6, 2016

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.