Path: utzoo!utgpu!water!watmath!clyde!bellcore!decvax!decwrl!sun!pitstop!sundc!seismo!uunet!ndsuvax!ncreed
From: ncreed@ndsuvax.UUCP (Walter Reed)
Newsgroups: comp.sys.amiga
Subject: Re: AmigaLine #4: - All about stacks - (Was Re: Setting Stack space...)
Keywords: STACKS
Message-ID: <617@ndsuvax.UUCP>
Date: 13 Jan 88 16:04:06 GMT
Reply-To: ncreed@ndsuvax.UUCP (Walter Reed)
Organization: North Dakota State University  Fargo, ND
Lines: 21

In article <126@forty2.UUCP> claudio@forty2.UUCP (Claudio Nieder) writes:
>In article <22330@ucbvax.BERKELEY.EDU> bryce@hoser (Bryce Nesbitt) writes:
>>       The icon that started you tool decides the stack size.  If the
>>    stack field is blank, then the default of ~4000 bytes is used.  The
>>    size is recorded in the normal task structures.
>I suggest the following improvment for 1.3:
>Instead of takeing the stack size from the icon that was double-clicked, the
>largest stacksize of all icons should be taken.
>                                        claudio
That would be a waste of memory.  What if the largest stack space of all the
icons is 100K?  How about looking at the process structure at the stacksize
field?  A program could check this, and if it is too small it could give
the user a message to increase the stack size and restart the application.
Is this possible or am I wrong?  (I was looking in dosextens.h)


-- 
Walter Reed              UUCP  : uunet!ndsuvax!ncreed
                      Internet : ncreed%NDSUVAX.BITNET@CUNYVM.CUNY.EDU
Ph 701-235-0774         Bitnet : ncreed@ndsuvax  OR NU105451@NDSUVM1
-------------------