Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!ucsd!rutgers!bellcore!tness7!tness1!sugar!peter
From: peter@sugar.uu.net (Peter da Silva)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Having your cake (Re: Address Space on the Amiga (was Re: Need info on exceptions))
Message-ID: <2599@sugar.uu.net>
Date: 8 Sep 88 12:13:29 GMT
References: <8808311759.AA19249@cory.Berkeley.EDU> <2582@sugar.uu.net> <4642@cbmvax.UUCP>
Organization: Sugar Land Unix - Houston, TX
Lines: 15

In article <4642@cbmvax.UUCP>, jesup@cbmvax.UUCP (Randell Jesup) writes:
> In article <2591@sugar.uu.net> peter@sugar.uu.net (Peter da Silva) writes:
> >Actually, the best way to do this would be to add a MEMF_PUBLIC flag to
> >each of the hunks, like the current MEMF_CHIP flag. Programs that break
> >can be fixhunked.

> 	I wasn't talking about load files, but AllocMem calls.  Load files
> are easy.

Well, fixing the load files will take care of most of the RKM problems,
which seem largely to be caused by programs using static data structures
for PUBLIC purposes. I suppose some programs will still break, but not too
many...
-- 
		Peter da Silva  `-_-'  peter@sugar.uu.net
		 Have you hugged  U  your wolf today?