Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!netnews.upenn.edu!msuinfo!convex.cl.msu.edu!jap
From: jap@convex.cl.msu.edu (Joe Porkka)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Good Programming stops guru |||| and BNF of C++
Message-ID: <1991Jan10.210636.6553@msuinfo.cl.msu.edu>
Date: 10 Jan 91 21:06:36 GMT
References: <4381@mindlink.UUCP>
Sender: news@msuinfo.cl.msu.edu
Organization: Michigan State University
Lines: 25

a976@mindlink.UUCP (Ron Tarrant) writes:

>> m0154@tnc.UUCP writes:


>There's another way to do this and you only have to run your program once.
>screen. Then, making sure you don't resize your CLI window, run your program,
>do whatever with your program, then quit. Select "flushlibs", then recheck the
>amount of free ram in the menubar. It should be the same as what you noted
>before running the program.

I dunno if this takes into account libs opening libs.
I have a program that does the following
 
	y=AvailMem(0)
	do {
	     x=y;
	     t=AllocMem(1<<31); /* Should fial :-) */
	     if(t!=0) {FreeMem(t,1<<31); break;}
	     y=AvailMem(0);
	} while(x<y);
	printf("%d %d\n", x, y);

This makes as much free mem as possible, even if open lib opens other
libs.