Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site well.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!gamma!epsilon!zeta!sabre!petrus!bellcore!decvax!ucbvax!ucdavis!lll-crg!well!fnf
From: fnf@well.UUCP (Fred Fish)
Newsgroups: net.micro.amiga
Subject: Re: Lattice C Problem
Message-ID: <423@well.UUCP>
Date: Sat, 4-Jan-86 17:32:06 EST
Article-I.D.: well.423
Posted: Sat Jan  4 17:32:06 1986
Date-Received: Mon, 6-Jan-86 03:11:20 EST
References: <2440@ukma.UUCP> <461@amiga.amiga.UUCP>
Reply-To: fnf@well.UUCP (Fred Fish)
Organization: Whole Earth 'Lectronic Link, Sausalito, CA
Lines: 20
Keywords: C

In article <461@amiga.amiga.UUCP> bruceb@hunter.UUCP (Bruce Barrett) writes:
>
>This type of "problem", I belive, is documented.  The "problem" is that
>the default stack setting (4000bytes) is to small.  I set the stack to

I have "stack 20000" in my Startup-Sequence file and have not found
too many things that won't compile or run.  Is anybody working on a compiler
that solves this stack problem transparently to the user.  This is one of
the few warts on an otherwise fine machine.  I have a couple ideas how it
could be done, but not real efficiently.  Even having a child process
allocate it's own stack at startup would be preferable.  One basic problem
the the current situation is that the parent process must know how much
stack all the the children it intends to run are going to need.


-- 

===============================================================================
Fred Fish  (415) 644-1230 ext 242  ucbvax!unisoft!fnf  well!fnf
===============================================================================