>>106973748
vla's are just a convenience, the criticisms that msvc has are legitimate.
just use alloca if you want a stack overflow, just check if the pointer is NULL, instead of just crashing.
In C++ you don't need to worry about it, all memory allocation failure just leads to a C++ exception, which leads to a debugger breakpoint if you don't catch it (basically the same result as abort / assert).
while in C if you use mallco or alloca, you just don't get an error, you need to print it yourself (unless you use a VLA, which I really don't like the fact it will stackoverflow, the reason I don't like it is because it makes error handling not very convenient, for example, if you wanted to use a crash handler to save unsaved changes to a file, or send a crash report logs or files with something like bugsplat, a stack overflow is not a very safe state for your application to be in, unless your signal handler has a separate stack, but I don't know how that works in windows, but I remember stack overflows are not very recoverable).
