Xref: utzoo comp.sys.amiga:13051 alt.flame:1392
Path: utzoo!hoptoad!amdahl!ames!ucbcad!pasteur!ucbvax!hoser.berkeley.edu!bryce
From: bryce@hoser.berkeley.edu (Bryce Nesbitt)
Newsgroups: comp.sys.amiga,alt.flame
Subject: Re: AmigaLine #4: - All about stacks - (Was Re: Setting Stack space...)
Keywords: STACKS
Message-ID: <22680@ucbvax.BERKELEY.EDU>
Date: 20 Jan 88 20:44:20 GMT
References: <617@ndsuvax.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: bryce@hoser.berkeley.edu (Bryce Nesbitt)
Followup-To: alt.flame
Organization: The Logic Foundation
Lines: 34

In article <617@ndsuvax.UUCP> ncreed@ndsuvax.UUCP (Walter Reed) writes:
>In article <126@forty2.UUCP> claudio@forty2.UUCP (Claudio Nieder) writes:
>>In article <22330@ucbvax.BERKELEY.EDU> bryce@hoser (Bryce Nesbitt) writes:
>>>
>>
>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)

#define FLAME_ON!

Look out folks, I'm about to sound like a grouch...  this posting symbolizes
exactly what is wrong with comp.sys.amiga.

Mr Reed, the first posting YOU QUOTED was dedicated ENTIRELEY to explaining
EXACTLY HOW TO CHECK THE STACK SIZE.

You ask "Is this possible or am I wrong?"  If you has bothered to read the
article you quoted before posting this speculative garbage you would have
known that it is not only posssible, but how to do it!  

	Think before you post.  Please!

#undef FLAME_ON!

BTW:  I thought before I sent this, and decided it was a bad idea.  So
much for a role-model :-).

|\ /|  . Ack! (NAK, SOH, EOT)
{o O} . bryce@hoser.berkeley.EDU -or- ucbvax!hoser!bryce (or try "cogsci")
 (")
  U	"As an engineer, I only set the value of a product... not the cost."
	-Bryce Nesbitt