mwm@pa.dec.com (Mike (My Watch Has Windows) Meyer) (01/26/91)
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.
<mike
--
Cheeseburger in paradise Mike Meyer
Making the best of every virtue and vice mwm@pa.dec.com
Worth every damn bit of sacrifice decwrl!mwm
To get a cheeseburger in paradisekdarling@hobbes.ncsu.edu (Kevin Darling) (01/26/91)
In <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? Yes, it could be done, but it sounds > like a lot of work for little benefit; better to modify it so that it > can handle more documents at once without bogging down). mwm@pa.dec.com (Mike (My Watch Has Windows) Meyer) replies: > Its primary application on the Amiga is to provide commands that start > about as fastly as running them from RAM, but don't require two copies > to be in RAM. [...] > 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. Much agreement with Mike. I'm glad he answered first <g>, because I tend to bristle at Amiga programmers who treat a 680x0 like a giant 6502; who can't handle writing reentrant code which the cpu was designed for. Unbelievable that a 68K user would want multiple copies of _any_ program code taking up extra memory. CPU/RAM dark ages! How many times have you heard: "Haha! THAT other OS requires programs with the entire kitchen sink built in, whereas on MY multitasking AMIGA I just run my favorite term program and editor in separate windows!" ?? Or talk about how proud they are of shared library code? Plus making fun of other OS's for "wasting lots of memory"? Huh! They should not take shots at other systems, and then turn a blind eye to the wastefulness of running multiple incarnations of any large and non-Pure applications on their own system... especially when it's so easy to have done it right to begin with. PS: this isn't a slam at Guy. Not his fault that CBM condoned non-reentrant code in the first place. Grrrr. :-) kevin <kdarling@catt.ncsu.edu>
m0154@tnc.UUCP (GUY GARNETT) (01/29/91)
In article <1991Jan26.075758.29203@ncsuvx.ncsu.edu> kdarling@hobbes.ncsu.edu (Kevin Darling) writes: >In <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. [Additional wrongheaded comments deleted] > >mwm@pa.dec.com (Mike (My Watch Has Windows) Meyer) replies: [Other lucid comments deleted; I stand corrected] >> 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. > >Much agreement with Mike. I'm glad he answered first <g>, because I tend >to bristle at Amiga programmers who treat a 680x0 like a giant 6502; >who can't handle writing reentrant code which the cpu was designed for. >Unbelievable that a 68K user would want multiple copies of _any_ program >code taking up extra memory. CPU/RAM dark ages! > [correct, slightly bristley comments deleted] I don't think of the 680x0 as a giant 6502! Actually, I think of it as a Z80 that died and went to heaven ... ;-) ;-) ;-) ;-) ;-) ;-) ;-) ;-) ;-) ;-) ;-) ;-) I guess it has something to do with where you learned to programm in assembly, huh? Anybody who missed the above smileys and wants to start a flame war is hereby directed to comp.sys.amiga.advocacy. Wildstar