creat 1219
He said shell. Which is an equivalent to the -20's exec.
Charlie Gibbs Exactly. Furthermore, one of the great arts is designing things so that the user can...
Memory management of the -20 side was one of its performance problems. I understood why the command parsing level was put into one segment that could be called at any time, but the tradeoff for this interface consistency was performance.
Huge gobs of core had parser in it rather than the code to do real work.
Which caused performance problems. For instance, everybody did a DA (daytime). TOPS-10 called its own internal routine and shipped the date-time stamp to the TTY. The -20 would have had to do all the paging and memory management of calling in the EXEC, parse the command, and eventually ship the date-time stamp to the TTY. Simple things that were done very often, shouldn't call in a moby segment of code as a user program layer.
run it So by monitor start the but even in
The Palm uses a stylus, which you might think is rat-like as it can be used for pointing, but it is actually used for a sort of gestural language that you might even like...
I don't believe that anyone has ever proposed that "straight" data entry is one of the tasks that is more efficiently done with a mouse. Still, varying the physical tasks done by a data entry...
And you have n copies of identical code in core, where n = jobs in use. It also requires that a user has to login to get the most basic system information because the EXEC was user mode code. Once you start adding to the list of commands that can be done not-logged-in, you start adding security holes if the command processing and dispatch is in a user mode program. There were reasons that having the monitor do the command processing and dispatching was a good idea.
BAH
Subtract a hundred and four for e-mail.