stops compiling

[Unknown W. Brackets]

I'm guessing it has to do with inlining or something similar where it's 
counting functions, but maybe I'm wrong.

Either way, 16,000 statements in the same scope are an obvious example 
of bad coding style ::).

And, my good sir, I strongly suggest you read this page:

http://redwing.hutman.net/~mreed/

Can you figure out which one you are :)?

-[Unknown]


> Walter Bright says...
>> It's a stack overflow in the compiler. No big deal, it'll be fixed in the 
>> next update. I kinda wonder, though, what purpose 16,000 statements serves? 
> 
> Wow, His Majesty is visiting the populace--and what seems He to be thinking: My
> bugs are manna for My choosen people, without Me they would starve in the
> desert.
> 
> What is the reason to stack a sequence of statements---and what is the reason
> for the runtime, that seems to be quadratic in the number of statements within
> the analyzed function? No answers please, He is the almighty.
> 
> 16,00 statemenst are too much? Forgive me Master, that was an inadequate try to
> initialize one of the prides of your creation, an associative array, with some
> 10,000 elements. Do not try to make Your novices convenient with your pride, You
> are almighty.    
> 
>