I agree. However, in this case execution speed isn't important at all because the routine is waiting for a human most of the time. And, the only way to conserve RAM is to inline the function calls to avoid using stack space -- not very interesting.


Again, I agree. I was doing it mostly as an exercise. I once took a class where the homework programs were graded based on how small you could make them. Although that is a very stupid way to teach programming, it was a lot of fun, even though I never had the smallest program in the class. Based on that, I'm actually surprised that nobody has found a way to shave another byte or two out of the line editor program. Probably it's because Jan's original program was so well optimized to begin with!

-- Russ