Newsgroups: comp.lang.dylan
Path: cantaloupe.srv.cs.cmu.edu!bb3.andrew.cmu.edu!news.sei.cmu.edu!cis.ohio-state.edu!math.ohio-state.edu!howland.reston.ans.net!europa.eng.gtefsd.com!news.umbc.edu!haven.umd.edu!ames!cnn.nas.nasa.gov!cnn!raible
From: raible@nas.nasa.gov (Eric Raible)
Subject: Re: Finalization
In-Reply-To: barmar@nic.near.net's message of 1 Oct 1994 18:06:15 -0400
Message-ID: <RAIBLE.94Oct3125019@win57.nas.nasa.gov>
Sender: news@cnn.nas.nasa.gov (News Administrator)
Nntp-Posting-Host: win57.nas.nasa.gov
Reply-To: raible@nas.nasa.gov
Organization: Applied Research Office, NASA Ames Research Center
References: <36erq3$c67@cantaloupe.srv.cs.cmu.edu> <36i2of$hsn@network.ucsd.edu>
	<36kmgn$oq@tools.near.net>
Date: Mon, 3 Oct 1994 19:50:19 GMT
Lines: 13


In article <36kmgn$oq@tools.near.net> barmar@nic.near.net (Barry Margolin) writes:

   I think the resurrection issue is only a problem if finalization is
   automatically implemented for all objects of some classes.  So long as it's
   done using some form of explicit registration, there shouldn't be a
   problem.

I don't see why "automatically for all objects of some class" and
"explicit registration" are at odds, since the obvious implementation
would be for initialization method to do the registration.

- Eric (raible@nas.nasa.gov)
