Path: utzoo!utgpu!attcan!uunet!tank!ncar!mailrus!tut.cis.ohio-state.edu!bloom-beacon!think!barmar From: barmar@think.COM (Barry Margolin) Newsgroups: comp.lang.c Subject: Re: memory allocation Message-ID: <28893@think.UUCP> Date: 29 Sep 88 21:21:20 GMT References: <1262@micomvax.UUCP> <733@proxftl.UUCP> <33184@cca.CCA.COM> <33692@XAIT.XEROX.COM> <6913@cdis-1.uucp> Sender: news@think.UUCP Reply-To: barmar@kulla.think.com.UUCP (Barry Margolin) Distribution: comp.lang.c,comp.os.misc Organization: Thinking Machines Corporation, Cambridge, MA Lines: 12 In article <6913@cdis-1.uucp> tanner@cdis-1.uucp (Dr. T. Andrews) writes: >I don't mind the small expense at free() time, because in general >that's not done nearly as often as malloc() in my applications. Shouldn't you free everything you allocate? Or do you just depend on everything being freed when you exit? Barry Margolin Thinking Machines Corp. barmar@think.com {uunet,harvard}!think!barmar