Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!mtune!codas!usfvax2!jc3b21!fgd3
From: fgd3@jc3b21.UUCP (Fabbian G. Dufoe)
Newsgroups: comp.sys.amiga
Subject: Re: A proposed solution to the resource tracking problem
Message-ID: <165@jc3b21.UUCP>
Date: Fri, 11-Sep-87 00:35:42 EDT
Article-I.D.: jc3b21.165
Posted: Fri Sep 11 00:35:42 1987
Date-Received: Sat, 12-Sep-87 19:55:58 EDT
References: <636@sugar.UUCP#
Organization: St. Petersburg Jr. College, FL
Lines: 28

in article <636@sugar.UUCP#, karl@sugar.UUCP (Karl Lehenbauer) says:
# The question often comes up on the net, "How can I kill my Amiga tasks?" or
# more often, "Why can't I kill my Amiga tasks?".  The problem, of course,
# is resource tracking, or more specifically the lack of support for it under
# AmigaDOS...
# 
# We should do that, too.  The memory allocation problem can be solved
# by using AllocRemember (Thanks, Peter, for showing me this).
# Library routines would front-end calls to create message ports and 
# such.  The library routines would keep track of what things need to
# be cleaned up on termination and how to do the cleanup in addition 
# to making the system calls to perform the specified operations.  The 
# _main (for C people) startup code would set up to receive a software 
# interrupt on the various control keys.  The interrupt would call the 
# code that cleans everything up.  
# 
     As I understand it, that is exactly how Lattice handles the problem
with version 3.10 of their C compiler.  I believe you have the option of
disabling that code, but the default is to trap BREAKs (^C) and put up a
requester asking if you wish to continue or abort.  Doesn't that pretty
well solve the problem for Lattice users?

--Fabbian Dufoe
  350 Ling-A-Mor Terrace South
  St. Petersburg, Florida  33705
  813-823-2350

UUCP: ...gatech!codas!usfvax2!jc3b21!fgd3