home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: chang.unx.sas.com!walker
- From: walker@chang.unx.sas.com (Doug Walker)
- Subject: Re: Ceck out this bug. What the *** is SASC/6.56 doing?
- Sender: news@unx.sas.com (Noter of Newsworthy Events)
- Message-ID: <DoGt57.IzK@unx.sas.com>
- Date: Mon, 18 Mar 1996 13:22:19 GMT
- X-Nntp-Posting-Host: chang.unx.sas.com
- References: <1120.6643T91T406@login.eunet.no> <885.6646T9T693@login.eunet.no> <Do9Fy0.HGp@unx.sas.com> <828.6649T501T491@login.eunet.no>
- Organization: SAS Institute Inc.
-
- In article <828.6649T501T491@login.eunet.no>,
- Patrick Hanevold <patrick.hanevold@login.eunet.no> wrote:
- >
- >>Stack EXTENSION, on the other hand, allows for a "fudge factor". If the
- >>remaining stack size at function entry time is less than the global long
- >>_STKNEED, a new stack extent is allocated. The default _STKNEED value
- >>is 400 bytes.
- > ^^^ This one is too little! It should be 4K by default. Like the OS.
-
- I disagree. It should be the maximum amount of stack that any system
- function or SAS/C library function will use. 1k should be plenty. You
- don't want to set _STKNEED too high, or you'll end up reallocating too
- often.
-
- You should change the value in your code by adding the following line
- external to any function:
-
- long _STKNEED = 1024;
-
- --
- *****
- *|_o_o|\\ Doug Walker walker@unx.sas.com
- *|. o.| ||
- | o |// Any opinions are mine, not those of SAS Institute, Inc.
- ======
-