Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!uunet!hsi!wright From: wright@hsi.UUCP (Gary Wright) Newsgroups: comp.sw.components Subject: Re: Re: Garbage Collection & ADTs Message-ID: <605@hsi86.hsi.UUCP> Date: 26 Sep 89 16:01:07 GMT References: <900@scaup.cl.cam.ac.uk> <6530@hubcap.clemson.edu> <909@scaup.cl.cam.ac.uk> <62342@tut.cis.ohio-state.edu> <599@hsi86.hsi.UUCP> <62546@tut.cis.ohio-state.edu> Reply-To: wright@hsi.com (Gary Wright) Organization: Health Systems Intl., New Haven, CT. Lines: 17 In article <62546@tut.cis.ohio-state.edu> Golden Richardwrites: >If the >programmer can't define when a certain object can go poof, I suspect >a serious lack of understanding of the problem at hand. But I wonder if the code is structured so that a programmer can define when a certain object can go "poof", whether the program can be understood by anyone other than the original programmer and whether the code can be easily reused. Unfortunately, I don't have a good example at hand (a major problem with this discussion in general, as has been noted by others). -- Gary Wright ...!uunet!hsi!wright Health Systems International wright@hsi.com