Article View: comp.sys.amiga.tech
Article #9691Re: Memory Allocation/Virtual Memory
From: Randell Jesup
Date: Sat, 03 Sep 1988 21:23
Date: Sat, 03 Sep 1988 21:23
11 lines
960 bytes
960 bytes
In article <3813@polya.Stanford.EDU> rokicki@polya.Stanford.EDU (Tomas G. Rokicki) writes:
>Worried about programs breaking because they didn't MEMF_PUBLIC?
...
>so why not add a MEMF_PRIVATE flag, where the default is MEMF_PUBLIC?
Exactly. New programs use it, old ones don't (by default, user
should be able to override at their own risk, or maybe some trick of changing
the default if a protection violation occurs, though it's risky).
--
Randell Jesup, Commodore Engineering {uunet|rutgers|allegra}!cbmvax!jesup
Technical Details
Message-ID:
<4657@cbmvax.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!cbmvax!jesupReferences:
<3813@polya.Stanford.EDU>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!cbmvax!jesup From: jesup@cbmvax.UUCP (Randell Jesup) Newsgroups: comp.sys.amiga.tech Subject: Re: Memory Allocation/Virtual Memory Message-ID: <4657@cbmvax.UUCP> Date: 3 Sep 88 21:23:46 GMT References: <3813@polya.Stanford.EDU> Reply-To: jesup@cbmvax.UUCP (Randell Jesup) Organization: Commodore Technology, West Chester, PA Lines: 11