Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!uw-june!uw-entropy!dataio!bright
From: bright@Data-IO.COM (Walter Bright)
Newsgroups: comp.lang.c
Subject: Re: malloced structure initilization
Message-ID: <1874@dataio.Data-IO.COM>
Date: 13 Feb 89 19:46:41 GMT
References: <202@sabin.UUCP> <8894@alice.UUCP>
Reply-To: bright@dataio.Data-IO.COM (Walter Bright)
Organization: Data I/O Corporation; Redmond, WA
Lines: 16

In article <8894@alice.UUCP< ark@alice.UUCP (Andrew Koenig) writes:
<In article <202@sabin.UUCP<, bjm@sabin.UUCP (Brendan J. McMahon) writes:
<< How do you initialize memory malloced for a structure without using calloc,
<< and without initilizing each structure element explicitly?
<How about this?
<	static struct foo init_foo;
<	struct foo *fp;
<	fp = (struct foo *) malloc (sizeof (struct foo));
<	*fp = init_foo;
<init_foo is guaranteed to be initialized because it's static.

Yah, and init_foo is guaranteed to be initialized to a 0 bit pattern,
just like if you called calloc instead of malloc. So where have you
gained anything here? I suggest that you declare init_foo something like:
	static struct foo init_foo = { 0,0L,0.0,(char *)0 };
or whatever is appropriate to the struct members.