Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!snorkelwacker!ira.uka.de!smurf!gopnbg!altger!doitcr!braaten.doit.sub.org!imuse.de.intel.com!netmuc!nixpbe!nixbur!linus!linus!luke.mitre.org!dsr
From: dsr@luke.mitre.org (Douglas S. Rand)
Newsgroups: comp.lang.lisp
Subject: Re: Destructors in Lisp and CLOS
Message-ID: <116852@linus.mitre.org>
Date: 13 Aug 90 14:08:11 GMT
References: <3296@stl.stc.co.uk> <116718@linus.mitre.org> <9862@rice-chex.ai.mit.edu>
Sender: usenet@linus.mitre.org
Reply-To: dsr@luke.mitre.org (Douglas S. Rand)
Distribution: comp.lang.lisp,uk.lisp
Lines: 17

In article <9862@rice-chex.ai.mit.edu>, rpk@wheaties.ai.mit.edu (Robert
Krajewski) writes:
|>Yes, but since the one of the breat benefits of Lisp is that you don't
|>have to write your own garbage collector, it would be nice to extend
|>it in ways that CLOS can exploit.
|>
|> ... Many reasons for it being a breat bennefit
I wasn't really passing judgement on the value.  Certainly it would be nice to 
know that you (the object) were about to be blown away so your resources could
be handled in a reasonable fashion.  I was just commenting on it not being a 
goal of CLOS or ANSI-X3J13.
                        
Douglas S. Rand 
Internet:   <dsrand@mitre.org>
Snail:	    MITRE, Burlington Road, Bedford, MA 
Disclaimer: MITRE might agree with me - then again...
Amateur Radio: KC1KJ