Article View: comp.sys.amiga.tech
Article #3561Re: De-Allocating Memory?
From: Dave Mc Mahan
Date: Wed, 09 May 1990 20:44
Date: Wed, 09 May 1990 20:44
18 lines
1259 bytes
1259 bytes
In article <29676@ut-emx.UUCP> greg@walt.cc.utexas.edu (Greg Harp) writes: >In article <MWM.90May8115606@raven.pa.dec.com> mwm@raven.pa.dec.com writes: >>Lattice's memory routines allocate a growing pool. Doing a free() >>doesn't release the memory back to the OS. > >Sin! Sin! Sin! PLEASE don't tell me Manx does the same thing!! Memory is too >much of a commodity in a multitasking machine to hog it like that! What >happens when an otherwise tame, small program wants to allocate a large >amount of memory just once, use it, and return it so OTHER PROGRAMS CAN HAVE >IT?!?!? That's why C= invented the AllocMem() and FreeMem() function calls. With not to much effort, you get EXACTLY what you want. >\\\\//// Greg Harp greg@ccwf.cc.utexas.edu -dave
Technical Details
Message-ID:
<11911@netcom.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!snorkelwacker!apple!netcom!mcmahanReferences:
<12750@wpi.wpi.edu> <MWM.90May8115606@raven.pa.dec.com> <29676@ut-emx.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!snorkelwacker!apple!netcom!mcmahan
From: mcmahan@netcom.UUCP (Dave Mc Mahan)
Newsgroups: comp.sys.amiga.tech
Subject: Re: De-Allocating Memory?
Message-ID: <11911@netcom.UUCP>
Date: 9 May 90 20:44:48 GMT
References: <12750@wpi.wpi.edu> <MWM.90May8115606@raven.pa.dec.com> <29676@ut-emx.UUCP>
Organization: NetCom- The Bay Area's Public Access Unix System {408 249-0290 guest}
Lines: 18