🚀 go-pugleaf

In article <14370@oberon.USC.EDU> papa@pollux.usc.edu (Marco Papa) writes:
>In article <3226@amiga.UUCP| jimm@cloyd.UUCP (Jim Mackraz) writes:
>|Hold on, here, fellas.  Is there a real reason to flush the font?  This thread
>|started when some guy thought the memory for an unused font was unavailable.
>
>|This isn't so that your customers feel that you've returned all your memory,
>|is it?  Or maybe to satisfy the BKDC rules or something.
>
>That's definitely THE main reason most third parties do the HUGE AllocMem,
>as the last thing before closing shop.
>
	Well, *I* never do that.  I suspect it's done by developers to see
if their code returned all the memory it allocted properly.

	Checking to see if everything get returned can be a bit of a pain,
particularly if you're working out of VD0: (which is not to slander VD0:).
My test cycle is:  avail, <program>, avail.  If the program opened
previously unopened libraries, then I do another <program>,avail cycle and
check the numbers.  In VD0:, this can be a problem, because it likes to free
up memory "every so often".  Thus, I often find myself saying "dir >NIL: :
OPT A" to try and make it happen more often so that the avail numbers don't
say I have more free memory that I started with.

_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
Leo L. Schwab -- The Guy in The Cape	INET: well!ewhac@ucbvax.Berkeley.EDU
 \_ -_		Recumbent Bikes:	UUCP: pacbell > !{well,unicom}!ewhac
O----^o	      The Only Way To Fly.	      hplabs / (pronounced "AE-wack")
"Work FOR?  I don't work FOR anybody!  I'm just having fun."  -- The Doctor