Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!milton!ogicse!pdxgate!qiclab!percy!data!kend
From: kend@data.UUCP (Ken Dickey)
Newsgroups: comp.lang.scheme
Subject: Re: Ports & GC
Message-ID: <485@data.UUCP>
Date: 2 May 91 16:24:18 GMT
References: <480@data.UUCP> <9104291751.AA10911@cymbal.reasoning.com.>
Organization: Microcosm, Beaverton, OR
Lines: 17

gyro@cymbal.reasoning.COM (Scott Layson Burson) writes:
>I have long thought that what UNWIND-PROTECT ought to mean is that the
>cleanup actions are performed when the continuation in which they were
>established becomes garbage.

>As Ken points out, this really isn't all that hard to implement.

A point of clarification.  I was referring to the implementation of a
finalization service on top of weak-pairs.  Weak pairs are very easy
to implement in a stop-and-copy (semi-space) collector.  Your mileage
may vary with other collection strategies.  Also, finalization is
related to lifetime/extent.  Unwind-protect deals more directly with
control flow.

{I still think its a good idea to turn off the motor (8-D)}.

-Ken					kend@data.uucp