yacc/bison incompatibility

Thread View: gnu.bash.bug

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Bill Trost,Box 607,ext 571,497 Fri, 17 Nov 1989 03:09

#743

Author: Bill Trost,Box 607,ext 571,497
Date: Fri, 17 Nov 1989 03:09

24 lines
1250 bytes

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

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads