Date: 20 Jul 1999 12:45:56 +0200 From: Dag-Erling Smorgrav <des@flood.ping.uio.no> To: John-Mark Gurney <gurney_j@resnet.uoregon.edu> Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>, freebsd-hackers@FreeBSD.ORG Subject: Re: Overcommit and calloc() Message-ID: <xzpk8rvbnvf.fsf@flood.ping.uio.no> In-Reply-To: John-Mark Gurney's message of "Tue, 20 Jul 1999 03:19:08 -0700" References: <002201bed217$e94beae0$291c453f@kbyanc.alcnet.com> <xzppv1nbpir.fsf@flood.ping.uio.no> <19990720031908.63115@hydrogen.fircrest.net>
next in thread | previous in thread | raw e-mail | index | archive | help
John-Mark Gurney <gurney_j@efn.org> writes: > Dag-Erling Smorgrav scribbled this message on Jul 20: > > When I allocate memory, I usually intend to put something in it. > > There's always the odd struct sockaddr_in which I bzero() before > > filling it in, but they're usually on the stack. > and even then, I don't believe in filling sockaddr_in w/ bzero, I > believe in using getsockaddr on it so that you actually get all the > fields filled out properly... See? One less reason to use bzero() / calloc() :) DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpk8rvbnvf.fsf>