Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!hellgate.utah.edu!dog.ee.lbl.gov!pasteur!cory.Berkeley.EDU!fadden
From: fadden@cory.Berkeley.EDU (Andy McFadden)
Newsgroups: comp.sys.apple2
Subject: Re: GS Curses
Message-ID: <12853@pasteur.Berkeley.EDU>
Date: 18 Apr 91 08:03:57 GMT
References: <8623@crash.cts.com>
Sender: news@pasteur.Berkeley.EDU
Reply-To: fadden@cory.Berkeley.EDU
Lines: 25

In article <8623@crash.cts.com> johnw@pro-harvest.cts.com (John Withers) writes:
>Why?  Curses was developed on slow (by today's standards) mini computers
>using serial communications.  We get acceptable Curses response via
>9600 BPS serial connections.  Although I don't have a GS, I don't think
>that even a //GS is that slow in character mode.

You might be surprised.

There is a *big* difference between APW with and without the "FastText" init.
I think the main consideration is using assembly to stuff things directly
onto the screen...  The C code that APW puts out for accessing single-byte
memory locations is pretty bad, so there would be a noticeable improvement
in speed if it were done in assembly (esp. since you can use short or DP
addressing).

Besides, why settle for "acceptable" response when you can have "instant"
response?

>John
><johnw@pro-harvest>

-- 
fadden@cory.berkeley.edu (Andy McFadden)
..!ucbvax!cory!fadden
fadden@hermes.berkeley.edu (when cory throws up)