🚀 go-pugleaf

In article <3719@tekig5.PEN.TEK.COM> brianr@tekig5.PEN.TEK.COM (Brian Rhodefer) writes:
>
>If calls on resource-allocation functions were made through a
>library of new accessing routines, it seems to me that automatic
>task-termination might be possible.  The 'rules' of the new routines
>would be that petitioners must SIMULTANEOUSLY specify not only the
>resources that they wish allocated (memory, I/O ports, libraries, etc),
>but the address of a 'cleanup' function as well.  The new routine would
>append the cleanup information to a linked list, and then pass off to
>the appropriate allocator.
>

Reading this I remember, that a Task-Structure contains a Cleanup_Code
pointer. However documentation about it is bad. 
What does the Standard-Cleanup do, and how do I (from "C") install my 
own CleanupCode? My Programs always have a central Cleanup-Code that
cleans up everything, if called from every point in the Program. 
So how do I get it there?

Cu
Markus
.-----------------------------------------------------------------.
|  shimoda@rmi.de       `---'   The last remaining adventure      |
|  shimoda@gopnbg.UUCP  |O o|   since there are no more tigers:   |
|                       ==Y==   Doublebuffered async. I/O       _ |
|----------------------- `U' ------------------------------  _ // |
|  Good terminalpackages     begin with A: AmigaCall, A-Ta.. \//  |
`-----------------------------------------------------------------'