Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!mit-eddie!genrad!decvax!linus!philabs!sbcs!sbstaff2!stark
From: stark@sbstaff2.UUCP (Eugene Stark)
Newsgroups: comp.sources.d,net.sources.bugs
Subject: Re: Termcap code in Phil's BASIC
Message-ID: <289@sbstaff2.UUCP>
Date: Fri, 19-Dec-86 11:32:16 EST
Article-I.D.: sbstaff2.289
Posted: Fri Dec 19 11:32:16 1986
Date-Received: Sun, 21-Dec-86 20:45:31 EST
References: <447@moncol.UUCP>
Organization: Computer Science Dept, SUNY@Stony Brook
Lines: 33
Xref: mnetor comp.sources.d:97 net.sources.bugs:918

> 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...
> 

I compiled Phil's BASIC on a SUN 3, and had the same problem with the
termcap.  I didn't feel like playing with it much, but I seem to recall
I did "adb" it, and noticed that the termcap library software was returning
an error when I didn't think it should have been.  Since I wasn't particularly
interested, and didn't immediately understand it, I gave up.

Gene Stark