Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!ut-sally!pyramid!amiga!dale From: dale@amiga.UUCP (Dale Luck) Newsgroups: comp.sys.amiga Subject: Re: 1.2 resident query Message-ID: <1614@amiga.amiga.UUCP> Date: Wed, 19-Nov-86 16:14:02 EST Article-I.D.: amiga.1614 Posted: Wed Nov 19 16:14:02 1986 Date-Received: Thu, 20-Nov-86 02:40:15 EST References: <1017@husc2.UUCP> <1607@amiga.amiga.UUCP> <760@ulowell.UUCP> <1005@cbmvax.cbmvax.cbm.UUCP> Reply-To: dale@tooter.UUCP (Dale Luck) Organization: Commodore-Amiga Inc., 983 University Ave #D, Los Gatos CA 95030 Lines: 36 In article <1005@cbmvax.cbmvax.cbm.UUCP> andy@skipper.UUCP (andy finkel) writes: >In article <760@ulowell.UUCP> page@ulowell.UUCP (Bob Page) writes: >>andy@skipper.UUCP (andy finkel) wrote in article <1607@amiga.amiga.UUCP>: >>>The resident command allowed a reentrant, sharable program to use kept >> ^^^^ note the tense here >> >>Even a _little_ more thought would have been nice ... like checksumming >>the segments to see if they had changed - if so, allocate space for >>new ones - in other words, take what you can and replace the dirty >>segments from the disk. I'm not flaming you guys, I'm flaming MCC. >> >Right. It was designed for BCPL programs, we put it into the >developer releases, it won't appear again until it works more generally. > >BTW, checksumming segments sounds like a poor idea...it defeats the >purpose of the shareable requirement...that 2 or more processes can share >the same copy of a program. Were you envisioning global variables ? Can we say, seperate I & D spaces? This can be implemented by using a global base register, like aztec C. Each invocation of the resident program would first checksome the 'code' area. If ok, the allocate a new 'data' area, initialize it and go. This does force a limit of 64k data space on 68000/6801x machines. But most programs can be written to deal with this, by forcing them to allocate the required data. > >>Hey, speaking of the Toolkit (well, you did but I trimmed out that part), >>what can you say about the program to allow overscanning? It's mentioned >>in the 1.2 release notes (poof) but the gamma 1 toolkit doesn't have it >>and the 1.2 release toolkit isn't out yet. >> The program you are refering to is morerows. I've got to hunt it down yet, make sure it works still and it will appear on the official toolkit release. Dale Luck officially representing duck. That's all folks.