Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!njin!limonce From: limonce@pilot.njin.net (Tom Limoncelli) Newsgroups: comp.sys.amiga.tech Subject: Re: Virtual Memory / doable 1.4 request Message-ID: Date: 19 May 89 16:56:31 GMT References: <8905181730.AA08602@postgres.Berkeley.EDU> Organization: NJ InterCampus Network, New Brunswick, N.J. Lines: 29 Maybe this is too weird. Maybe there aren't many spare bits left in the MEM_* flags (I don't have an Amiga here at work so I can't check if it's a word or a long word) but why not have MEM_PHYSICAL *and* MEM_VIRTUAL? Obviously, it would be an error to include both and if you don't include either it would default to MEM_PHYSICAL. Then C-A could publish that when they release version x.y (2.0?) that the default would be switch to MEM_VIRTUAL. This would give publishers time to update their programs. Maybe the switch doesn't have to be an a particular release, it could be in preferences. You would only have to have it set to MEM_PHYSICAL until you've received the last update on the last piece of your software that doesn't support the "virtual standard". All that publishers would have to do for the update is include MEM_PHYSICAL xor MEM_VIRTUAL in every Alloc(). I think a good time for this would be in the 1.4 release. Since Commodore is warning publishers that they may have to send "1.4 updates" to their users (because 1.4 may break some things) they might as well be asked to update their Alloc() calls. They could write an AWK script to just make them all MEM_PHYSICAL if they are lazy! Whaddya think? -- Tom Limoncelli -- tlimonce@drunivac.Bitnet -- limonce@pilot.njin.net Drew University -- Box 1060, Madison, NJ -- 201-408-5389 Standard Disclaimer: I am not the mouth-piece of Drew University