Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c++,comp.lang.c Subject: Re: alloca()-support Date: Tue, 01 Oct 2019 02:42:34 -0700 Organization: None to speak of Lines: 13 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader02.eternal-september.org; posting-host="278a65e792fa58e42a0648a4551fd282"; logging-data="14574"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+5eRwjwananO9/DaSDzBXf" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:aP2iN4nydA1CQ52CxLH6MAvizoc= sha1:/Yrt7aIgIDNnP6I6X+9qG2Nxopk= Xref: csiph.com comp.lang.c++:68842 comp.lang.c:146495 Robert Wessel writes: [...] > Are C++ compilers actually obligated to define _STDC_NO_VLA_? No, __STDC_NO_VLA__ (note the double underscores) is specific to C11 and later. C++ doesn't support VLAs at all, so there's no need for a C++ compiler to indicate its lack of support, and the C++ standard doesn't require it to do so. -- Keith Thompson (The_Other_Keith) kst-u@mib.org Will write code for food. void Void(void) { Void(); } /* The recursive call of the void */