From: Jared Hance <jaredhance@gmail.com>
To: git@vger.kernel.org
Subject: Re: [RFC] struct *_struct
Date: Thu, 5 Aug 2010 18:43:21 -0400 [thread overview]
Message-ID: <20100805224321.GA22430@localhost.localdomain> (raw)
In-Reply-To: <AANLkTin_6gaYF++N2GBgDsedfo7mY7yG5H99=-DxCa5E@mail.gmail.com>
On Thu, Aug 05, 2010 at 11:20:14AM -0500, Michael Witten wrote:
> On Wed, Aug 4, 2010 at 14:24, Junio C Hamano <gitster@pobox.com> wrote:
> > I hate... "typedef foo struct foo"
>
> How come?
In my opinion, it creates ambiguity. If I have
typedef struct foo foo;
And I have "foo" used in a code snippet, it is much less easier to see
if foo is being used in the type context or if its an instance, since
I like to do
struct foo foo;
which reads much less well as:
foo foo;
Its also much less easier to grep though to find all the places the
type is used. If I do
$ git grep "foo"
I will end up with the instances and the struct type. whereas I can do
$ git grep "struct foo"
to find (most|all) of the types, depending on whether the code uses
decent practices (there shouldn't be a second space between struct and
foo, or a newline between them).
I could also use a similar regular expression to find all the
instances (ie, all the instances of foo that aren't prefixed with
struct).
next prev parent reply other threads:[~2010-08-05 22:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 15:08 [RFC] struct *_struct Jared Hance
2010-08-04 19:24 ` 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 [this message]
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=20100805224321.GA22430@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).