Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!decwrl!labrea!rutgers!mit-eddie!fenchurch.mit.edu!jbs From: jbs@fenchurch.MIT.EDU (Jeff Siegal) Newsgroups: comp.lang.c Subject: Re: alloca(), #if, and other controversial things... Message-ID: <9912@eddie.MIT.EDU> Date: 20 Aug 88 05:48:43 GMT References: <8808171410.AA05337@ucbvax.Berkeley.EDU> <1259@garth.UUCP> Sender: uucp@eddie.MIT.EDU Reply-To: jbs@fenchurch.MIT.EDU (Jeff Siegal) Organization: MIT EE/CS Computer Facilities, Cambridge, MA Lines: 10 In article <1259@garth.UUCP> smryan@garth.UUCP (Steven Ryan) writes: [...](While heap storage includes local storage, heaps are almost always slower; using an indirect address instead of a stack base+offset screws up the optimiser; remember to release everything at the end screws up the programmer. Local storage is a no-fuss, no-bother, no-problem solution to a need I have in near most every program I write.) Take a look at Scheme. Jeff Siegal