Xref: utzoo comp.unix.wizards:9120 comp.lang.c:10569
Path: utzoo!utgpu!water!watmath!clyde!ima!haddock!karl
From: karl@haddock.ISC.COM (Karl Heuer)
Newsgroups: comp.unix.wizards,comp.lang.c
Subject: Re: Alloca() and friends
Message-ID: <4419@haddock.ISC.COM>
Date: 6 Jun 88 16:04:48 GMT
References: <16018@brl-adm.ARPA> <8017@brl-smoke.ARPA> <1874@thebes.UUCP>
Reply-To: karl@haddock.ima.isc.com (Karl Heuer)
Followup-To: comp.lang.c
Organization: Interactive Systems, Boston
Lines: 12

In article <1874@thebes.UUCP> schwartz@thebes.UUCP (Scott Schwartz) writes:
>[gcc allows "foo(s) int s; { int a[s]; ... }".]
>I think this obviates the need for alloca() in most (all?) cases.
>Too late to get it in ansi, I suppose.

Yes, I'm sure it's much too late to get it into ANSI C-88, if indeed it ever
had a chance.  But this is exactly the right way to get it into C-99 (or
whenever __STDC__==2 comes out): by including it as a nonconforming extension
in popular compilers, the ramifications ought to be well-understood by then.

Karl W. Z. Heuer (ima!haddock!karl or karl@haddock.isc.com), The Walking Lint
Followups to comp.lang.c.