From:	marg AT okstate DOT edu (Carl Marg)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Allegro problem
Date:	Wed, 03 Mar 1999 22:58:47 GMT
Organization:	Oklahoma State University
Lines:	21
Message-ID:	<36ddbe74.1569380@news.okstate.edu>
References:	<36dd9087 DOT 274233 AT news DOT okstate DOT edu> <36DD8294 DOT CA280436 AT unb DOT ca> <36dda03b DOT 4295162 AT news DOT okstate DOT edu>
NNTP-Posting-Host:	x8b4e504a.dhcp.okstate.edu
Mime-Version:	1.0
X-Newsreader:	Forte Agent 1.5/32.452
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

On Wed, 03 Mar 1999 20:58:05 GMT, marg AT okstate DOT edu (Carl Marg) wrote:

>On Wed, 03 Mar 1999 14:42:28 -0400, Endlisnis <s257m AT unb DOT ca> wrote:
>
>>    Well, there are a few [possible] problems.  First of all, you may be
>>running out of stack space depending on what resolution you are using.  If
>>your area is 1000x1000 then you could get more than 2000 levels of recursion.
>>And with 5 4-byte integers plus some stack overhead for each call you have way
>>more than 40k on the stack.  I don't know what the default size of a stack is
>>in DJGPP, but it can be changed.
>>    Also, this function would crash if it was run outside of a completely
>>closed figure because it never checks to see if it is off of the screen.
>
>my last trial was in a closed figure - 300x300 area
>it only does a small part of the fill before it crashes.
>Then it will do anything from gpf to hard lock to rebooting my
>computer. 
on the other hand, I think it must be the stack, I tried it for a very

small figure, and it worked all right
Now I just need to figure out how to change the stack size...

- Raw text -