RE: [GD-Windows] autodocument max stack usage

[Brian H. <bri...@py...>]

> I take it you're not a fan of alloca() :-)

Speaking of alloca(), I'm on the record for thinking it's one of the
least understood and most underutilized functions out there.  Incredibly
handy when you're worried about memory fragmentation.

> Unfortunately, pretty much any executable will link against 
> the standard C library, which uses recursion in parts, so 
> even if your program doesn't use recursion, there's no way of 
> proving that your stack size is enough (and no way for a tool 
> to report on potential maximum stack usage).

More important, why is the size of the stack an issue, other than for
informative reasons?  I generally just crank the hell out of my stack in
the linker settings.  It shouldn't have any side effects, assuming I
don't use all of it.

Brian