Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!ucsfcgl!kneller
From: kneller@cgl.ucsf.edu (Don Kneller)
Newsgroups: comp.lang.c++
Subject: Re: C++ for DOS/OS2
Keywords: C++, Glockenspiel, DOS
Message-ID: <11895@cgl.ucsf.EDU>
Date: 24 Sep 89 22:33:10 GMT
References: <661@windy.dsir.govt.nz> <1456@dinl.mmc.UUCP> <672@windy.dsir.govt.nz> <4109@pegasus.ATT.COM>
Sender: daemon@cgl.ucsf.edu
Lines: 30

hansen@pegasus.ATT.COM (Tony L. Hansen) writes:

>< I haven't found this very satisfactory; I still need to use a batch file
>< and avoid 'make' to do my big files. If you use this roll out mechanism
>< compile times can rise amazingly - say from 100 seconds to 2000 seconds.

>When I use one of the cfront ports under DOS, I found this small trick
>useful. Because cfront can run out of memory so easily, even using make can
>push things over the limit. So instead of running make directly to build
>things, I run it indirectly via a small batch file:

>mk.bat
>	make -n %1 %2 %3 %4 %5 %6 %7 %8 %9 > tmp.bat
>	tmp

The disadvantage of this technique is that "mk.bat" won't stop if a
compiler error happens.

At the risk of sounding like a plug, my OPUS MAKE program swaps
itself from memory before spawning its shell lines, reducing its
memory requirements to about 3K. I can supply more information to
anyone who is interested.

- Don Kneller
  OPUS Software
  (415) 664-7901
-----
	Don Kneller
UUCP:		...ucbvax!ucsfcgl!kneller
INTERNET:	kneller@cgl.ucsf.edu