Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sdd.hp.com!decwrl!pa.dec.com!bacchus!mwm From: mwm@pa.dec.com (Mike (My Watch Has Windows) Meyer) Newsgroups: comp.sys.amiga.misc Subject: Resident Applications (Was: True Multitasking) Message-ID: Date: 25 Jan 91 17:37:33 GMT References: <42149@nigel.ee.udel.edu> <672@tnc.UUCP> <42598@nigel.ee.udel.edu> <678@tnc.UUCP> Sender: news@pa.dec.com (News) Organization: Missionaria Phonibalonica Lines: 37 In-Reply-To: m0154@tnc.UUCP's message of 24 Jan 91 16:23:14 GMT In article <678@tnc.UUCP> m0154@tnc.UUCP (GUY GARNETT) writes: Yes, I am talking about the same image in memory. The well defined exception I am talking about is when pure code is made resident. This is usually used for system level code, cli commands, and the like; I don't think it is indended that applications programs be made resident (can you imagine re-coding wordperfect so that it is pure, and then making it resident? Sorry, but "resident" code is meant for any application that can use it. Remember, on the Amiga it buys you more than just shared code for multiple running copies. Its primary application on the Amiga is to provide commands that start about as fastly as running them from RAM, but don't require to copies to be in RAM. Its a godsend for doing a large compile, as all the parts of the compiler are resident. Both C compilers for the Amiga support "compile this as resident"; its trivial to make a C program resident (assuming its small enough). If you have a program that's running a good percentage of the time, and is liable to be started a large number of times, making it resident is a good idea. I can see how someone might have Word Perfect in that category; after all, most editors are. Residentable editors is SOP these days, so it ought to be the same for Word Perfect. I've got plenty of RAM, so I tag almost all commands that are pure as autoloaded resident, and build anything that I expect to be run more than once between boots as pure.