Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!aplcen!haven!udel!ee.udel.edu
From: new@ee.udel.edu (Darren New)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Memory Protection!
Message-ID: <28131@nigel.ee.udel.edu>
Date: 22 Aug 90 12:28:13 GMT
References: <1145.26bd4989@waikato.ac.nz> <1410050@hpcvca.CV.HP.COM>
Sender: usenet@ee.udel.edu
Organization: University of Delaware
Lines: 13
Nntp-Posting-Host: estelle.ee.udel.edu

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.  

Of course, the compilers do indeed implement resource tracking. If you are
writing code that you will run on both Unix and the Amiga, you will probably
be using malloc(), free(), fopen(), fclose(), and so on.  All the C compilers
on the Amiga implement these and track the resources you use so that exit()
will free the resources. Don't sweat it.          -- Darren

-- 
--- Darren New --- Grad Student --- CIS --- Univ. of Delaware ---