Path: utzoo!utgpu!attcan!uunet!husc6!think!ames!oliveb!pyramid!leadsv!laic!nova!darin
From: darin@nova.laic.uucp (Darin Johnson)
Newsgroups: comp.lang.c
Subject: Re: Is malloc() or calloc() "better"?
Message-ID: <403@laic.UUCP>
Date: 5 Jan 89 18:21:19 GMT
References: <gables.416@umigw.miami.edu> <eaCKX#4UXCPK=eric@snark.UUCP> <46929@yale-celray.yale.UUCP>
Sender: news@laic.UUCP
Reply-To: darin@nova.UUCP (Darin Johnson)
Organization: Lockheed AI Center, Menlo Park
Lines: 8

Actually, calloc() is not always a shell around malloc()!  On an early
Pyramid, I had spent lots of wasted time tracking down a bug, that fixed
itself when I used free() for malloc()ed objects, and cfree() for
calloc()ed objects.  In the buggy version, free() was used for
everything...

Darin Johnson (leadsv!laic!darin@pyramid.pyramid.com)
	"You can't fight in here! This is the war room.."