Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!decwrl!megatest!djones
From: djones@megatest.UUCP (Dave Jones)
Newsgroups: comp.lang.c
Subject: Re: alloca() portability
Message-ID: <14560@goofy.megatest.UUCP>
Date: 28 Nov 90 22:00:19 GMT
References: <1990Nov24.035618.11358@zoo.toronto.edu>
Organization: Megatest Corporation, San Jose, Ca
Lines: 14

From article <1990Nov24.035618.11358@zoo.toronto.edu>, by henry@zoo.toronto.edu (Henry Spencer):
> In article <14517@megatest.UUCP> djones@megatest.UUCP (Dave Jones) writes:
>>> A proper fix is
>>> impossible without language changes.
>>
>>Isn't the change simply to legitimize alloca(), letting the compiler
>>in on the gag?  That's what Sun did.
> 
> Please *read* the article you are responding to!  Memory allocation is only
> one small fragment of the general problem of cleanup-on-return, and often not
> the most important one.  I was addressing the general problem.
> -- 
> "I'm not sure it's possible            | Henry Spencer at U of Toronto Zoology
> to explain how X works."               |  henry@zoo.toronto.edu   utzoo!henry