Path: utzoo!utgpu!watmath!uunet!tut.cis.ohio-state.edu!cs.utexas.edu!usc!samsung!caesar.cs.montana.edu!ogccse!reed!trost
From: trost@reed.bitnet (Bill Trost,Box 607,ext 571,497)
Newsgroups: gnu.bash.bug
Subject: yacc/bison incompatibility
Message-ID: <13592@reed.UUCP>
Date: 17 Nov 89 03:09:08 GMT
Sender: news@reed.UUCP
Lines: 24

Just for the record, the incompatibility (only one, right? :-) )
between yacc and bison is still there.  Namely, the sequence of
commands:

bash$ for i in a b; do
bash> echo $i
bash> done
`done' is not a valid identifier.

happens like this if I use yacc, but works just fine if I use bison.
This occurs on:

a Vax running 4.3
a Decstation 3100 running Ultrix pretending to be a Vax running Bsd
a Tektronix 4317 running Utek 4.0 pretending to be a Sun3 running Bsd

Oh, note that there seems to be some problems using the Sun3
configuration for the Tek workstation, but I have yet to look at it
closely.  One possibility is that it should pretend to be running
sunOS3 instead of Bsd, but I am writing a thesis (honest :-) ) so I
haven't much time to play with such things.

AND, note that previous bug involving xterm occured on more than one
machine.  (Yes, I check these things....)