Path: utzoo!utgpu!watserv1!ria!obelix!ptoper
From: ptoper@obelix (Andy Nagy)
Newsgroups: comp.sys.amiga.advocacy
Subject: Re: Amiga OS *IS* state of the art
Message-ID: <2637@ria.ccs.uwo.ca>
Date: 2 Apr 91 21:02:17 GMT
References: <12393@pasteur.Berkeley.EDU> <1003@cbmger.UUCP> <7827@jhunix.HCF.JHU.EDU> <8806@gollum.twg.com>
Sender: news@ria.ccs.uwo.ca
Reply-To: ptoper@obelix (Andy Nagy)
Lines: 35

In article <12393@pasteur.Berkeley.EDU>, navas@cory.Berkeley.EDU (David
C. Navas) writes:

[stuff deleted]

> >>		-	Resource tracking

> If you *really* need resource tracking, it's a week project -- maybe three
> weeks for 2.0 [because there are more system structures and stuff to learn].
> Just use self-identifying data structures, and free everything according to 
> its type via library calls.  Implementation is left up to the imagination
> of the reader.  It's not quite that simple, but it ain't hard neither.

[stuff deleted]

> Like I said, it's probably a week job for 1.3.  malloc already does it for
> every memory allocation.  All you need is screens, windows, etc. pointers to
> which are kept in a linked list which identifies the data.  The rest is
> so simple, I might write it one of these days for kicks.
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^


	Please keep us posted ...

  

> David Navas                                   navas@cory.berkeley.edu



-------------------------------------------------------------------------------
Andy Nagy (ptoper@asterix.gaul.csd.uwo.ca)
The University of Western Ontario, London, Canada
 "Dee do do do, dee da da da, thats all I want to say to you" -- The Police