Newsgroups: comp.sys.amiga.programmer
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!alberta!herald.usask.ca!ccu.umanitoba.ca!kaarts
From: kaarts@ccu.umanitoba.ca (Kenneth John Aarts)
Subject: setting stack size in source code
Message-ID: <1991Apr30.001538.4655@ccu.umanitoba.ca>
Summary: how to set stack size
Organization: University of Manitoba, Winnipeg, Canada
Distribution: na
Date: Tue, 30 Apr 91 00:15:38 GMT
Lines: 26

I sent a letter to Sas asking how to set the stack size in the source code.
Their reply was to include the line

	long _stack = n;

where n is the stacksize in bytes. The source code must then be either linked
with cres.o or cback.o. I would suggest cres.o since I understood that cback.o
required some other variables to be initialized , specifically what to use for
stdio.

	I had also asked them about the possibility of combining cback.o and
cres.o. They replied that they were not considering this option because there
was no concievable need for it, and the concepts were mutually exclusive. My
thinking is:
	say I want to write a program that takes a mounted device name for an
	arguement, and opens a window which is just a title bar that displays
	the free space for that device.

	It seems to me that I would want this program to be run in the 
background and hence, I would need to use cback.o. On the other hand I would 
like to run this program for several devices, so it is a prime candidate for
cres.o. I realize that there are other ways around this, possibly even better,
but the point is that this is a valid requirement. 
	Does anyone have any comments? 
	Ken