Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!ukma!nrl-cmf!ames!ucbcad!ucbvax!jade!ig!uwmcsd1!csd4.milw.wisc.edu!john1233
From: john1233@csd4.milw.wisc.edu (Thomas M Johnson)
Newsgroups: comp.sys.atari.8bit
Subject: Re: ACTION! Language
Message-ID: <3631@uwmcsd1.UUCP>
Date: Tue, 24-Nov-87 11:04:37 EST
Article-I.D.: uwmcsd1.3631
Posted: Tue Nov 24 11:04:37 1987
Date-Received: Sat, 28-Nov-87 06:02:54 EST
References: <4204@watdragon.waterloo.edu>
Sender: daemon@uwmcsd1.UUCP
Reply-To: john1233@csd4.milw.wisc.edu.UUCP (Thomas M Johnson)
Distribution: comp
Organization: University of WI-Milwaukee
Lines: 14
Keywords: ACTION!, compilers, memory manager

In article <4204@watdragon.waterloo.edu> rastroobossc@violet.waterloo.edu (Rick Stroobosscher) writes:
>
>  I am currently developing a run-time memory manager for the Action 
>programming language.  This run-time manager will serve two functions.  
>First, it will allow for dynamic memory allocation and disposal.  The function
>New () takes as input the size of a requested block and returns an address
>to this block.  The procedure Dispose takes as input the address of a block
>and returns it to the internal heap.

The Action! toolkit contains an include file called
ALLOCATE.ACT and it allows dynamic memory usage. I don't know if it
is as nice as yours though, I never tried using it.

					 Tom