Path: utzoo!attcan!uunet!seismo!ukma!rutgers!rochester!pt.cs.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu!jh4o+ From: jh4o+@andrew.cmu.edu (Jeffrey T. Hutzelman) Newsgroups: comp.sys.apple2 Subject: Re: MacMusings Message-ID: Date: 25 Oct 90 16:48:21 GMT References: <139800043@uxa.cso.uiuc.edu>, <90295.214849SAB121@psuvm.psu.edu> Organization: Carnegie Mellon, Pittsburgh, PA Lines: 13 In-Reply-To: <90295.214849SAB121@psuvm.psu.edu> I agree. Apple II code always has been tight and clean; there's no other way to do it on a 6502. People who start to program on 68000's or 8086's find that they have all this memory and all these registers, and they start using it all without thinking about it. On a system like the Apple II where resources (time, memory, registers) are short, you have to think about it. ----------------- Jeffrey Hutzelman America Online: JeffreyH11 Internet/BITNET:jh4o+@andrew.cmu.edu, jhutz@drycas.club.cc.cmu.edu, jh4o@cmuccvma >> Apple // Forever!!! <<