Path: utzoo!attcan!uunet!van-bc!ubc-cs!news-server.csri.toronto.edu!rutgers!usc!wuarchive!decwrl!bacchus.pa.dec.com!deccrl!shlump.nac.dec.com!jareth.enet.dec.com!edp
From: edp@jareth.enet.dec.com (Eric Postpischil (Always mount a scratch monkey.))
Newsgroups: comp.sys.handhelds
Subject: Re: Elek-Tek, flicker, Amiga owners, free memory
Message-ID: <15765@shlump.nac.dec.com>
Date: 3 Oct 90 12:02:10 GMT
References: <4016@tellab5.tellabs.com>
Sender: newsdaemon@shlump.nac.dec.com
Reply-To: edp@jareth.enet.dec.com (Eric Postpischil (Always mount a scratch monkey.))
Organization: Digital Equipment Corporation
Lines: 25

In article <4016@tellab5.tellabs.com>, ram@tellabs.com (Bob Martin) writes:

>2) Free Memory:  When I do an ON-C, and then an immediate MEM command, I get
>	30213.5 in 1:.  If I do a drop to clear 1:, and then immediately do
>	another MEM, I get 30200.  After a few minutes of calculations, followed
>	by a CLEAR and PURGE of all variables, I'll get a number somewhere
>	in the 29K range.  Is there some way of doing garbage collection
>	without doing an ON-C?

The MEM command performs garbage collection.  You are getting smaller results
because some memory is in use.  The calculator remembers certain things:  The
stack as it was before the last command, the arguments of the last command, the
last four command lines entered, and the last program in which DOERR was issued,
if the argument was a string.

If you've entered large command lines recently, they are still around, taking up
more memory than if only small lines had been entered recently.

You can clear the last stack, arguments, and command lines by going into the
mode menu and turning off and on each of those options.  You can clear the
retention of the last program that issued DOERR with a string by executing 0
DOERR.


				-- edp