Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!necntc!ames!aurora!labrea!decwrl!sun!texsun!sundc!citcom!jack
From: jack@citcom.UUCP (Jack Waugh)
Newsgroups: comp.sys.amiga
Subject: Re(2): resource tracking
Message-ID: <73@citcom.UUCP>
Date: Thu, 3-Sep-87 00:11:55 EDT
Article-I.D.: citcom.73
Posted: Thu Sep  3 00:11:55 1987
Date-Received: Sat, 5-Sep-87 10:09:39 EDT
References: <1708@amiga.amiga.UUCP> <350@palladium.UUCP>
Organization: Citcom Systems, Inc., Herndon, VA
Lines: 12


Maybe what we need is reference-counted objects.
Of course, libraries already are, but you'd have
to extend that to other resources.  Like Smalltalk
objects, each object would point (through some amount
of indirection and/or mapping) to a procedure to
delete it.  Every object (such as a process) that
could have references to other objects would have
to maintain a list of the objects referenced.  Circular
garbage would be possible, but I don't think this
would be a practical problem on a machine that
gets rebooted every few weeks.