Xref: utzoo comp.lang.c:38123 comp.terminals:2770
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!bu.edu!snorkelwacker.mit.edu!hsdndev!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.lang.c,comp.terminals
Subject: Re: getchar and EOF (was: One more point regarding = and == (more flamage))
Message-ID: <6406:Apr1014:09:3691@kramden.acf.nyu.edu>
Date: 10 Apr 91 14:09:36 GMT
References: <1991Apr4.215605.2801@syssoft.com> <1991Apr7.064003.8552@athena.mit.edu> <3727@inews.intel.com>
Followup-To: comp.terminals
Organization: IR
Lines: 15

In article <3727@inews.intel.com> bhoughto@nevin.intel.com (Blair P. Houghton) writes:
> (the ascii-only assumption is bogus at the
> outset, since it ignores the loadable (8-bit) fonts of most
> ANSI terminals, of which DEC VT character terminals are a
> near conformant).

I would phrase that as ``since it ignores the loadable (8-bit) fonts of
most VT-compatible terminals, of which ANSI terminals are a near
conformant.'' Let's keep straight who copied whose models here.

(I really wish ANSI hadn't futzed with the entirely reasonable VT
end-of-line behavior. But I'm afraid this is getting a bit far from
comp.lang.c, so followups to comp.terminals.)

---Dan