Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!cs.utexas.edu!uunet!crdgw1!vdsvax!perley
From: perley@vdsvax.crd.ge.com (Perley Donald P)
Newsgroups: comp.sys.amiga
Subject: Re: stack
Message-ID: <9130@vdsvax.crd.ge.com>
Date: 16 Aug 89 19:08:27 GMT
References: <16943@ut-emx.UUCP>
Reply-To: perley@vdsvax.crd.ge.com (Perley Donald P)
Organization: General Electric CRD, Schenectady, NY
Lines: 21

In article <16943@ut-emx.UUCP> sjk@ut-emx.UUCP (sjk) writes:
>2)  What do I lose by always runnig with a larger stack so I don't
>    run my programs, forgetting to change the stack, and wind up
>    visiting meditation heaven?

As someone pointed out, programs with small stack requirements
will get large stacks, chewing up your available memory.

One advantage to running programs from the workbench (icon clicking),
is that you can specify the stack size in the icon file, and automatically
get a large one for programs that need it.  

I think one of the process spawning programs lets you specify stack
size (maybe "runbg, but I'm not sure).  Using this in conjuction with an
alias in your startup file would also let you get a big stack
everytime you run that monster program.


-- 
-don perley
perley@crd.ge.com