From owner-freebsd-hackers Tue Jul 20 3:46:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 25DCB152D3 for ; Tue, 20 Jul 1999 03:46:02 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id MAA08747; Tue, 20 Jul 1999 12:45:56 +0200 (CEST) (envelope-from des) To: John-Mark Gurney Cc: Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG Subject: Re: Overcommit and calloc() References: <002201bed217$e94beae0$291c453f@kbyanc.alcnet.com> <19990720031908.63115@hydrogen.fircrest.net> From: Dag-Erling Smorgrav Date: 20 Jul 1999 12:45:56 +0200 In-Reply-To: John-Mark Gurney's message of "Tue, 20 Jul 1999 03:19:08 -0700" Message-ID: Lines: 14 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John-Mark Gurney 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