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

Re: Purpose of "struct object_entry *oe = oe;"?

From
BSBruce Stephens <bruce.stephens@isode.com>
Date
Jul 2, 2010, 09:28 UTC
Message-ID
<80iq4y44h8.fsf@tiny.isode.net>
In-Reply-To
<20100702084846.GA4682@gmail.com>
David Aguilar <davvid@gmail.com> writes:
[...]
> There are some good explanations in the list archives.
> http://thread.gmane.org/gmane.comp.version-control.git/133278/focus=133422
> http://thread.gmane.org/gmane.comp.version-control.git/124676/focus=124803
Thanks.  That matches my guess.
Wouldn't it be useful to mention it in CodingGuidelines?

A danger is that the declaration (that yes, this really is initialised before use) becomes invalid during further changes, so it's best if everybody concerned understands the convention.

Obviously if it's a commonly understood and used convention then it's just as well not to have it in CodingGuidelines, but I'm not convinced that this one is, though (having noticed it) the intention isn't hard to grok.

Previous: David Aguilar
Message 4 of 4 in “Purpose of "struct object_entry *oe = oe;"?”
  1. Bruce StephensJun 29, 2010
  2. Joshua JuranJul 2, 2010
  3. David AguilarJul 2, 2010
  4. Bruce StephensJul 2, 2010

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.