Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!adam.pika.mit.edu!scs
From: scs@adam.pika.mit.edu (Steve Summit)
Newsgroups: comp.unix.wizards
Subject: Re: alloca (was: libpw.a)
Message-ID: <10939@bloom-beacon.MIT.EDU>
Date: 29 Apr 89 04:36:07 GMT
References: <157@dftsrv.gsfc.nasa.gov> <10013@smoke.BRL.MIL> <8184@chinet.chi.il.us> <1250@frog.UUCP> <564@aablue.UUCP> <1883@thor.acc.stolaf.edu> <15945@rpp386.Dallas.TX.US> <10090@smoke.BRL.MIL> <8261@chinet.chi.il.us>
Sender: daemon@bloom-beacon.MIT.EDU
Reply-To: scs@adam.pika.mit.edu (Steve Summit)
Lines: 12

In article <8261@chinet.chi.il.us> les@chinet.chi.il.us (Leslie Mikesell) writes:
%In article <10090@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn) writes:
%>[earlier posters wrote:]
%>>>To repeat: alloca is EVIL.
%>>It doesn't have to be.
%>There is no situation I know of when use of alloca() is necessary.
%There are two situations which are helped by the use of alloca():
%...
%2) providing the ability to longjmp() out of a function (or just return)
%with the no longer needed memory automatically released

longjmp is evil.