Hacker News Reader

Is the normal stack size for a thread still 8MB? Most of my c++ has always been simulation or signal processing where a buffer of objects to be simulated or samples/pixels to be processed always exceed sane stack sizes. The standard answer is to preallocate these buffers and reuse them. Smart pointers are pretty useful in the simulation case, but not really necessary for the signal processing.

which works great until you need more than 8MiB of memory.

stack is usually quite limited unless you very much control the environment

How do you create recursive data structure on the stack?

Using pointers to the stack?

Pointers to stack sound like a recipe for disaster (all those pointers will be dangling very very soon).

I’d argue it’s safer to have the paradigm of “i own stuff then delegate it you” (ie down the stack) then the non hierarchy chaos the heap invites