Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!batcomputer!rpi!rpi.edu!deven
From: deven@rpi.edu (Deven Corzine)
Newsgroups: comp.sys.amiga.tech
Subject: Re: MEMF_PHYSICAL?
Message-ID: <DEVEN.89May19054021@daniel.rpi.edu>
Date: 19 May 89 09:40:21 GMT
References: <8905181642.AA07593@postgres.Berkeley.EDU>
Sender: usenet@rpi.edu
Organization: RPI Public Access Workstation Lab, Troy NY
Lines: 18
In-reply-to: dillon@POSTGRES.BERKELEY.EDU's message of 18 May 89 16:42:21 GMT

In article <8905181642.AA07593@postgres.Berkeley.EDU> dillon@POSTGRES.BERKELEY.EDU (Matt Dillon) writes:

           MEMF_PUBLIC is so badly defined that most people use it
   incorrectly...  either that or allocate all of their memory
   MEMF_PUBLIC.  It has essentially become a random flag and as such
   should be phased out (with the bit eternally reserved to mean
   nothing).

Indeed.  Certainly a thought to consider.  But, that will annoy many
people who've been including it all this time "for future
compatibility"...  :-)

Deven
--
shadow@[128.113.10.2]   <shadow@pawl.rpi.edu> Deven T. Corzine (518) 272-5847
shadow@[128.113.10.201] <shadow@acm.rpi.edu>  2346 15th St.    Pi-Rho America
deven@rpitsmts.bitnet   <userfxb6@rpitsmts>   Troy, NY 12180-2306  <<tionen>>
"Simple things should be simple and complex things should be possible." - A.K.