Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!pasteur!ames!eos!shelby!polya!rokicki From: rokicki@polya.Stanford.EDU (Tomas G. Rokicki) Newsgroups: comp.sys.amiga.tech Subject: Re: Saving (and finding it again) memory Message-ID: <9794@polya.Stanford.EDU> Date: 7 Jun 89 22:37:07 GMT References: <108611@sun.Eng.Sun.COM> Sender: Tomas G. Rokicki Organization: Stanford University Lines: 19 In article <108611@sun.Eng.Sun.COM>, page%swap@Sun.COM (Bob Page) writes: > dwl10@uts.amdahl.com (Dave Lowrey) wrote: > > 1. Have a program allocate & initialize some memory > > 2. That program exits. > > 3. Have another program be able to find that memory. > Here's an ugly way to do it - have the program 'mark' the start Just call AddLibrary() with a proper library structure. A library doesn't necessarily have to have functions (except two or three very simple ones) and it can have any amount of data. By setting the open count to `1' or greater, the thing will stay in memory---and it can be reclaimed and freed easily when necessary. References: `set' (on a very early fish disk by yours truly) and `mylib' (on another fish disk by Jim Mackraz.) Go for it! -tom