Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!mit-eddie!mintaka!olivea!samsung!usc!sdd.hp.com!uakari.primate.wisc.edu!aplcen!haven!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: scope of malloc
Message-ID: <14413@smoke.brl.mil>
Date: 10 Nov 90 05:33:48 GMT
References: <1990Nov07.134942.7355@virtech.uucp> <1990Nov7.234315.15508@athena.mit.edu> <3729@skye.ed.ac.uk>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 5

In article <3729@skye.ed.ac.uk> richard@aiai.UUCP (Richard Tobin) writes:
>You have the choice of rejecting machines or compilers with such serious
>deficiencies as making alloca() impossible.

What nonsense.  Being unlike a VAX is hardly a "serious deficiency".