Re: > fails. Because heaps are unlimited whilst stacks are not.

bart wrote:

>
Maybe the routine is never called. Or it's called once then never called
again but the stack is now committed.
>

as far as i know it is not commited..im not 100 procent sure (as it would probably need to use soem tool that shows that, maybe there are some) but probably what i think is rught
windows will swap unused pages away from ram and it work in runtime
i mean if you declare 300 MB stack use it once and then for an hour you use only 2 MB of this the 298 MB of physical ram will nt be "taken"
it is not hard to do it in system i think just as aplication acces ram thry some table you may monitor once a time which regions are alocated and non used and "detatch " phisical ram ftom thsi area - then attach it if there is an acces -0 where this detach and attach is not very slow operation
thats how i see it..i readed something about this but not much and long time ago