From: Jared Hance <jaredhance@gmail.com>
To: git@vger.kernel.org
Subject: [RFC] struct *_struct
Date: Wed, 4 Aug 2010 11:08:43 -0400 [thread overview]
Message-ID: <20100804150843.GA2762@localhost.localdomain> (raw)
After browsing some of the diff related code today, I noted the
structure "struct diff_queue_struct". I found it somewhat odd that a
struct had struct in the name of the struct, and I hadn't really seen
any others like this.
Indeed, there are two others: struct dir_struct and struct cmd_struct.
To see, you can run:
$ git grep _struct *.c *.h
Typing "struct *_struct" is rather verbose - We already have to
prepend the "struct", so it is extremely clear that we are using a
struct. Is there a reason that:
- We are extremely verbose
- We use this style in only 3 cases
next reply other threads:[~2010-08-04 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 15:08 Jared Hance [this message]
2010-08-04 19:24 ` [RFC] struct *_struct Junio C Hamano
2010-08-04 21:38 ` [PATCH] Refactor structures in the form of *_struct Jared Hance
2010-08-05 16:20 ` [RFC] struct *_struct Michael Witten
2010-08-05 22:43 ` Jared Hance
2010-08-06 3:57 ` Michael Witten
2010-08-06 12:29 ` Jared Hance
2010-08-06 2:28 ` Miles Bader
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100804150843.GA2762@localhost.localdomain \
--to=jaredhance@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.
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 NNTP newsgroup(s).