Path: utzoo!attcan!uunet!husc6!bloom-beacon!mit-eddie!uw-beaver!ssc-vax!shuksan!tahoma!hrsw2!bakken
From: bakken@hrsw2.UUCP (David E. Bakken)
Newsgroups: comp.sys.amiga
Subject: Re: SH program
Summary: hogging stack space isn't hard
Message-ID: <82@hrsw2.UUCP>
Date: 16 May 88 14:39:48 GMT
References: <2092@cadovax.UUCP>
Organization: Boeing Commercial Aircraft Co., Seattle, Wa.
Lines: 18

In article <2092@cadovax.UUCP>, keithd@cadovax.UUCP (Keith Doyle) writes:
> 
> What are these guys doing that takes up so much stack space?  Seems to me
> you have to try pretty hard to create a program that hogs up so much.  
> I've never had ANY problem with ANY program I've been working on with
> regards to stack.  Why is everyone else having so much trouble?
> 
I'm working on a plotting program that prints postscript and to epson-like
printers.  It currently needs 100K-150K of stack space to not bomb with normal
sets of points in the epson quadrouple density mode.  That's not the
graphics sort of stack hogging you were asking about but it is one
example where a large stack is needed.

-- 
Dave Bakken   Boeing Commercial Airplanes		(206) 277-2571
uw-beaver!apcisea!hrsw2!bakken
Disclaimer: These are my own views, not those of my employers.  Don't
let them deter you from buying the 747 you've been saving hard for.