Xref: utzoo rec.arts.sf-lovers:49710 alt.cyberpunk:5036 comp.arch:19335 Path: utzoo!utgpu!cs.utexas.edu!hellgate.utah.edu!caen!math.lsa.umich.edu!zaphod.mps.ohio-state.edu!usc!elroy.jpl.nasa.gov!zardoz.cpd.com!dhw68k!felix!frogger From: frogger@felix.UUCP (frogger) Newsgroups: rec.arts.sf-lovers,alt.cyberpunk,comp.arch Subject: Re: 6502 interrupts (was Re: Count Zero Interrupt) Message-ID: <153869@felix.UUCP> Date: 15 Nov 90 02:00:42 GMT References: <1427@carol.fwi.uva.nl> <4bC2VW600VIE094FUA@andrew.cmu.edu> Reply-To: frogger@felix.UUCP (frogger) Organization: The Pond Lines: 23 In article ap1i+@andrew.cmu.edu (Andrew C. Plotkin) writes: > I dearly love my old Apple 2; but I have to admit that the 6502 handles > interrupts the way a drunk gorilla handles fine china. In article esmith@goofy.apple.com (Eric Smith) writes: >The 6502 handles interrupts just fine; it is the Apple II that handles >them badly. The design philosopy was apparently the same as that of >Doc Suding (sp?) of The Digital Group fame (anybody remember them?): >interrupts are hard to understand so you shouldn't use them. Yes, I remember Dr. Suding and the Digital Group. In fact, I have quite a bit of Digital Group equipment collecting dust in the garage. Not too shabby for the day. And there _was_ an obvious bias against interrupts, but everything always seemed to hold together without them. The wait-state logic was pretty buggered up, too. Caused me a bit of grief when I wanted to run a DSDD floppy and the TV-80 board at the same time. (But we digress, for a note that is crossposted to such an eclectic set of groups.)