Path: utzoo!utgpu!news-server.csri.toronto.edu!helios.physics.utoronto.ca!ists!yunexus!oz From: oz@yunexus.yorku.ca (Ozan Yigit) Newsgroups: comp.lang.misc Subject: Re: Closures (was Re: class-sic.) Message-ID: <20842@yunexus.YorkU.CA> Date: 21 Jan 91 16:04:44 GMT References: <20058@yunexus.YorkU.CA> <27942:Jan902:20:0791@kramden.acf.nyu.edu> <27770.278aef90@kuhub.cc.ukans.edu> <22345:Jan1021:30:4591@ <1991Jan21.120628.2749@waikato.ac.nz> Sender: news@yunexus.YorkU.CA Organization: York U. Communications Research & Development Lines: 28 In article <1991Jan21.120628.2749@waikato.ac.nz> ldo@waikato.ac.nz (Lawrence D'Oliveiro, Waikato University) writes: >Is there anybody else left in the world who thinks closures are >a pretty neat idea, and a damned (pardon my French) useful programming >technique? I would think that the entire Scheme community may be more than just anybody, for example. ;-) >... Some LISP hackers seem to think they've got >closures too, but they haven't--all they've got is an almost-as-useful >kludge that requires call frames to be allocated on the heap. I do not know what you mean by almost-as-useful, as you are not specific as to what is missing from, say scheme closures. The call frames are not required to be on the heap at all times, they can be moved there when necessary. (see [1] for example) oz --- [1] William D. Clinger, Anne H. Hartheimer and Eric M. Ost, Implementation Strategies for Continuations, Conference Record of the 1988 ACM Conference on Lisp and Functional Programming, August 1988, 124 131. --- We only know ... what we know, and | Internet: oz@nexus.yorku.ca that is very little. -- Dan Rather | UUCP: utzoo/utai!yunexus!oz