Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!ucla-cs!zen!ucbvax!CORY.BERKELEY.EDU!dillon From: dillon@CORY.BERKELEY.EDU (Matt Dillon) Newsgroups: comp.sys.amiga Subject: Re: A proposed solution to the resource tracking problem (long) Message-ID: <8709091634.AA19588@cory.Berkeley.EDU> Date: Wed, 9-Sep-87 12:34:52 EDT Article-I.D.: cory.8709091634.AA19588 Posted: Wed Sep 9 12:34:52 1987 Date-Received: Fri, 11-Sep-87 04:08:57 EDT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 32 >>CONCLUSION: >> The end result would be that we would then be able to kill new >>programs which understand the new EXEC calls and still not be able to kill >>old programs which do not. > >Argh!!! I think this is a _very_ wrong approach. You see, it says "Every >last person who _ever_ writes _any_ software must know about this and >use it. *All* of you, every one. And, you must do it correctly.". >Chances of getting everybody to do this are so near zero as to be >uncountable. Think of all the software now that uses busy waits, >or MOVE SR, or any other forbidden fruit. >If it's done like that, 5 years from now there will still be untrackable >software that will force people to suffer from reboots, lost resources, >whatever. No, you simply have one call to EXEC 'TrackResource(TRUE)'. Presumably the major compilers (Manx/Lattice) would incorporate this into their assembly code. Commodore isn't stable enough (yet) to be able to release a new OS which makes half the software in existance incompatible. I have an idea: Make the resource tracking contingent on a new DOS. That is, if C-A releases a new DOS *everybody* will use it, and we can make the resource tracking 'forced' automatically upon any program using the new DOS (as well as have the EXEC calls mentioned above). Reason: Anybody who knows about the new DOS (Assuming C-A releases one) would also know about the automatic resource tracking and write their programs accordingly. Is that convoluted or What? -Matt