Re: [boost] Bug with gcc and array

Do have a reference for me were to find the implementation limits?

<snip/> ulimit on UNIX-like operating systems.

Would it a good idea to add a static assert to boost::array that ensures that the array size is small enough? I think a error message at compile time is more help full than Segmentation fault at run time. On UNIX-like operating systems, the available stack size is usually defined at run-time, and can often be tweaked per process. How much stack memory you can safely allocate and use depends on that, so it's hard to provide a compile time error.

Jens