git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Bruce Stephens <bruce.stephens@isode.com>
To: David Aguilar <davvid@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Purpose of "struct object_entry *oe = oe;"?
Date: Fri, 02 Jul 2010 10:28:51 +0100	[thread overview]
Message-ID: <80iq4y44h8.fsf@tiny.isode.net> (raw)
In-Reply-To: <20100702084846.GA4682@gmail.com> (David Aguilar's message of "Fri, 2 Jul 2010 01:48:48 -0700")

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.

      reply	other threads:[~2010-07-02  9:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-29 12:28 Purpose of "struct object_entry *oe = oe;"? Bruce Stephens
2010-07-02  1:43 ` Joshua Juran
2010-07-02  8:48 ` David Aguilar
2010-07-02  9:28   ` Bruce Stephens [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=80iq4y44h8.fsf@tiny.isode.net \
    --to=bruce.stephens@isode.com \
    --cc=davvid@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).