Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!van-bc!rsoft!mindlink!a218
From: a218@mindlink.UUCP (Charlie Gibbs)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Memory Protection!
Message-ID: <2905@mindlink.UUCP>
Date: 21 Aug 90 21:43:52 GMT
Organization: MIND LINK! - British Columbia, Canada
Lines: 26

In article <1410050@hpcvca.CV.HP.COM> charles@hpcvca.CV.HP.COM
(Charles Brown) writes:

>The only reason I was concerned about this is because on the Amiga you
>*must* deallocate all that RAM because the system does not implement
>resource tracking.  I mentioned to him that I intended to do this in
>all my code.  He told me it was a bad idea for code which would be
>used on Unix.  So now the best solution I know of is to place this
>within #ifdef's which include the deallocation only if the target
>machine is an Amiga.

     Being relatively new to Unix, I'm curious about this.  Is it
really that much of a Bad Thing to clean up after yourself, or are
we falling into the trap of quibbling over a few milliseconds when
our time would be better spent elsewhere?

     Just on general principles, I like to leave things as I found
them.  Besides, if time was critical, I would probably be using
static memory anyway (no pun intended).

     So could a Unix guru please enlighten me?  Is it actually
considered evil to free memory yourself, or is it one of those
conventions that just grew?

Charlie_Gibbs@mindlink.UUCP
I'm trying to develop a photographic memory.