freebsd-nq

History

David E. O'Brien 17e6630760 Revert the past 3 commits to what should have been the rev 1.18 -> rev 1.19 change. (doesn't anybody read commit logs and look at the diffs?)		1999-07-30 15:05:32 +00:00
..
test	Regenerate to match changes made in the embedded yacc parser.	1999-07-23 23:13:44 +00:00
ACKNOWLEDGEMENTS
closure.c
defs.h	Add support for Bison's "%expect <int>" directive.	1999-07-29 08:42:21 +00:00
error.c
lalr.c
lr0.c
main.c
Makefile
mkpar.c	Add support for Bison's "%expect <int>" directive.	1999-07-29 08:42:21 +00:00
NEW_FEATURES
NOTES
output.c
reader.c	Add support for Bison's "%expect <int>" directive.	1999-07-29 08:42:21 +00:00
README
skeleton.c	Revert the past 3 commits to what should have been the rev 1.18 -> rev 1.19	1999-07-30 15:05:32 +00:00
symtab.c
verbose.c
warshall.c
yacc.1
yyfix.1
yyfix.sh	Check that user supplied the required argument; and if not, show usage().	1999-07-29 09:47:33 +00:00

README

    Berkeley Yacc is an LALR(1) parser generator.  Berkeley Yacc has been made
as compatible as possible with AT&T Yacc.  Berkeley Yacc can accept any input
specification that conforms to the AT&T Yacc documentation.  Specifications
that take advantage of undocumented features of AT&T Yacc will probably be
rejected.

    Berkeley Yacc is distributed with no warranty whatever.  The code is certain
to contain errors.  Neither the author nor any contributor takes responsibility
for any consequences of its use.

    Berkeley Yacc is in the public domain.  The data structures and algorithms
used in Berkeley Yacc are all either taken from documents available to the
general public or are inventions of the author.  Anyone may freely distribute
source or binary forms of Berkeley Yacc whether unchanged or modified.
Distributers may charge whatever fees they can obtain for Berkeley Yacc.
Programs generated by Berkeley Yacc may be distributed freely.

    Please report bugs to

			robert.corbett@eng.Sun.COM

Include a small example if possible.  Please include the banner string from
skeleton.c with the bug report.  Do not expect rapid responses.