From: Shawn Pearce <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/3] Remove unsupported C99 style struct initializers in git-archive.
Date: Sun, 5 Nov 2006 02:36:34 -0500 [thread overview]
Message-ID: <20061105073634.GA4616@spearce.org> (raw)
In-Reply-To: <7vd582uz5b.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> "Shawn O. Pearce" <spearce@spearce.org> writes:
>
> > +static struct archiver_desc
> > +{
> > + const char *name;
> > + write_archive_fn_t write_archive;
> > + parse_extra_args_fn_t parse_extra;
> > +} archivers[] = {
> > + { "tar", write_tar_archive, NULL },
> > + { "zip", write_zip_archive, parse_extra_zip_args },
> > };
>
> If this were a struct with bazillions of fields I might have had
> trouble swallowing the change, but this is so small that it is
> no brainer.
Right; if it was larger I would have been in trouble. :-)
> I think this actually is an improvement.
>
> > static int run_remote_archiver(const char *remote, int argc,
> > @@ -88,7 +86,10 @@ static int init_archiver(const char *nam
> >
> > for (i = 0; i < ARRAY_SIZE(archivers); i++) {
> > if (!strcmp(name, archivers[i].name)) {
> > - memcpy(ar, &archivers[i], sizeof(struct archiver));
> > + memset(ar, 0, sizeof(*ar));
> > + ar->name = archivers[i].name;
> > + ar->write_archive = archivers[i].write_archive;
> > + ar->parse_extra = archivers[i].parse_extra;
>
> But is this change really needed? Shouldn't a structure
> assignment just work?
No, they are different structs...
Which I did to reduce the size of the initializer (see above)
so that it was a no brainer for you to swallow. :-)
--
prev parent reply other threads:[~2006-11-05 7:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-05 5:37 [PATCH 3/3] Remove unsupported C99 style struct initializers in git-archive Shawn O. Pearce
2006-11-05 7:32 ` Junio C Hamano
2006-11-05 7:36 ` Shawn Pearce [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061105073634.GA4616@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.