From: Andreas Schwab <schwab@issan.informatik.uni-dortmund.de>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: Thomas.Koenig@ciw.uni-karlsruhe.de, egcs@cygnus.com
Subject: Re: Mini-patch for cccp.c
Date: Tue, 07 Oct 1997 03:48:00 -0000 [thread overview]
Message-ID: <vyzk9fpzxnj.fsf@issan.informatik.uni-dortmund.de> (raw)
In-Reply-To: <199710070006.UAA23461@caip.rutgers.edu>
Kaveh R Ghazi <ghazi@caip.rutgers.edu> writes:
|>> Tue Sep 30 16:50:55 CEST 1997 Thomas Koenig (ig25@rz.uni-karlsruhe.de)
|>>
|>> * cccp.c:
|>> (expand_to_temp_buffer) initialize all members of obuf
|> Having to remember to init structure members when new ones are
|> added is prone to error. Isn't it better to do bzero(&foo, sizeof(foo))
|> and then set any non zero members?
Pedantically this won't work for pointers in the structure, ie. they still
have to be initialized explicitly. Or initialize it with a prototype
static variable that is implicitly initialized.
--
Andreas Schwab "And now for something
schwab@issan.informatik.uni-dortmund.de completely different"
next prev parent reply other threads:[~1997-10-07 3:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-06 18:10 Kaveh R. Ghazi
1997-10-07 3:48 ` Andreas Schwab [this message]
1997-10-08 2:55 ` Kamil Iskra
1997-10-08 21:19 ` Joern Rennecke
1997-10-07 11:41 ` Jeffrey A Law
-- strict thread matches above, loose matches on Subject: below --
1997-10-08 14:14 meissner
1997-10-01 11:08 Peter Seebach
1997-10-01 11:14 ` Joe Buck
1997-10-01 12:17 ` Chip Salzenberg
[not found] <no.id>
1997-09-30 8:09 ` Thomas Koenig
1997-09-30 23:24 ` Jeffrey A Law
1997-10-06 8:25 ` Thomas Koenig
1997-09-30 6:01 Thomas Koenig
1997-09-30 23:21 ` Jeffrey A Law
1997-10-01 2:43 ` Thomas Koenig
1997-10-01 7:07 ` Paul Koning
1997-10-01 8:36 ` Thomas Koenig
1997-10-01 9:36 ` Chip Salzenberg
1997-10-01 12:02 ` Lee Iverson
1997-10-01 12:17 ` Chip Salzenberg
1997-10-06 16:43 ` Jeffrey A Law
1997-10-06 17:13 ` John Carr
1997-10-06 17:47 ` Jeffrey A Law
1997-10-06 16:49 ` Jeffrey A Law
1997-10-06 16:30 ` Jeffrey A Law
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=vyzk9fpzxnj.fsf@issan.informatik.uni-dortmund.de \
--to=schwab@issan.informatik.uni-dortmund.de \
--cc=Thomas.Koenig@ciw.uni-karlsruhe.de \
--cc=egcs@cygnus.com \
--cc=ghazi@caip.rutgers.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).