Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!ut-emx!sjk
From: sjk@ut-emx.UUCP (bob)
Newsgroups: comp.sys.amiga
Subject: Re: Is she c:Stack'd
Summary: let's talk about this
Message-ID: <19086@ut-emx.UUCP>
Date: 3 Oct 89 03:08:51 GMT
References: <3944@m2-net.UUCP> <8053@cbmvax.UUCP>
Organization: The University of Texas at Austin, Austin, Texas
Lines: 26

Dave Haynie writes:
> in article <3944@m2-net.UUCP>, ba@m2-net.UUCP (Bill Allen) says:
> 
> 
  > What causes certain prgs to work just fine in 4K of stack
  > (or less) while others need 10K?  I've seen several that
  > require 20K, 30K, 40K.  Can other programming techniques be
  > used to prevent this?  
  
> The difference usually amounts to something like this:
> [exampes deleted]

Dave, you're probably right, the average programmer probably does
not know how much stack he is using, or even wonder, perhaps.  So
what constructs are there that require stack use?  I am a novice
C programmer and while I am capable of writing some relatively
complex code, I don't yet know enough about the internal operations
to know what structures use how much stack and why.  Where can I
learn this kind of stuff?  I think it would prove quite useful.  I
already have a few programs that need stacks ~50K and have no idea
why; it would be great to be able to change this!

Thanks,
Scot
sjk@astro.as.utexas.edu
Bdah!- M