Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!clyde!cuae2!ihnp4!houxm!hjuxa!petsd!moncol!john
From: john@moncol.UUCP (John Ruschmeyer)
Newsgroups: comp.sources.d,net.sources.bugs
Subject: Termcap code in Phil's BASIC
Message-ID: <447@moncol.UUCP>
Date: Mon, 15-Dec-86 11:57:48 EST
Article-I.D.: moncol.447
Posted: Mon Dec 15 11:57:48 1986
Date-Received: Thu, 18-Dec-86 01:44:17 EST
Distribution: net
Organization: Monmouth College, W. Long Branch, NJ
Lines: 33
Keywords: BASIC, termcap, tc=
Xref: mnetor comp.sources.d:81 net.sources.bugs:913

Has anyone else had luck bringing up the recently-posted BASIC interpreter
(Phil's BASIC) on a machine other than the four mentioned in the posting?
 
Aa co-worker and I have tried to bring it up on a Perkin-Elmer 3220 running
Edition VII, a Perkin-Elmer 3250 running XELOS (SVr2), and an IBM-PC AT
running SCO XENIX/286. In all three cases, we have had problems related to
the termcap code.

In all three cases, it was necessary to make the interpreter default to no
editor for it to work with most termcap entries.

In the best case, the editor would function correctly with very simple
termcaps (adm3, pe550, etc.).

Under no circumstances, would the editor work with a termcap that referred
to another entry by way of a 'tc=' entry. Depending on the system, either a
'BAD TERMCAP ENTRY' message is returned or the program goes into
never-never land.


Has anyone else noticed problems with the termcap code? If so, what did you
have to do to fix it?

Thanks in advance...

-- 
Name:		John Ruschmeyer
US Mail:	Monmouth College, W. Long Branch, NJ 07764
Phone:		(201) 571-3557
UUCP:		...!vax135!petsd!moncol!john	...!princeton!moncol!john
						   ...!pesnta!moncol!john

	If you give bigger kisses, you get bigger hugs.