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: <DoKGIF.HAx@unx.sas.com>
- Date: Wed, 20 Mar 1996 12:39:51 GMT
- X-Nntp-Posting-Host: chang.unx.sas.com
- References: <1120.6643T91T406@login.eunet.no> <828.6649T501T491@login.eunet.no> <DoGt57.IzK@unx.sas.com> <755.6652T1180T2805@login.eunet.no>
- Organization: SAS Institute Inc.
-
- In article <755.6652T1180T2805@login.eunet.no>,
- Patrick Hanevold <patrick.hanevold@login.eunet.no> wrote:
- >
- >>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.
- >
- >Well, its a little dificult subject.
- >
- >>You should change the value in your code by adding the following line
- >>external to any function:
- >
- >> long _STKNEED = 1024;
- >
- >Yeah, it will do, but its a litte anoying having it in the source though.
-
- OK, then use OML to break up the library, get rid of the module that defines
- _STKNEED, replace it with a better definition, use OML to recreate the library,
- and quit whining.
-
-
-
- --
- *****
- *|_o_o|\\ Doug Walker walker@unx.sas.com
- *|. o.| ||
- | o |// Any opinions are mine, not those of SAS Institute, Inc.
- ======
-