Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!tut!news
From: pl@etana.tut.fi (Lehtinen Pertti)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Memory Protection!
Message-ID: <1990Aug23.141738.9830@funet.fi>
Date: 23 Aug 90 14:17:38 GMT
References: <2905@mindlink.UUCP>
Sender: news@funet.fi (#News )
Organization: Finnish University and Research Network FUNET
Lines: 25


From article <2905@mindlink.UUCP>, by a218@mindlink.UUCP (Charlie Gibbs):
> In article <1410050@hpcvca.CV.HP.COM> charles@hpcvca.CV.HP.COM
> (Charles Brown) writes:
> 
> Is it actually considered evil to free memory yourself,
> or is it one of those conventions that just grew?
> 

	For me it's very natural to free all my memory after use,
	but in UNIX forgetting to do so does not lead to missing memory
	blocks.  System anyway releases all resources it has given to process. 

	malloc/free only allocate/release memory already owned by process,
	and if they run out of memory, they ask more with system call (sbreak).
	
	So every call to malloc/free doesn't (in UNIX) lead to system call and
	so it is quite efficient there.

--

	
pl@tut.fi				! All opinions expressed above are
Pertti Lehtinen				! purely offending and in subject
Tampere University of Technology	! to change without any further
Software Systems Laboratory		! notice