freebsd-skq/usr.bin/yacc
2002-04-04 20:58:27 +00:00
..
test
ACKNOWLEDGEMENTS
closure.c remove __P 2002-03-22 01:42:45 +00:00
defs.h remove __P 2002-03-22 01:42:45 +00:00
error.c Follow suit with OpenBSD and NetBSD and tell the program name in diagnostics. 2002-04-04 20:58:27 +00:00
lalr.c remove __P 2002-03-22 01:42:45 +00:00
lr0.c remove __P 2002-03-22 01:42:45 +00:00
main.c remove __P 2002-03-22 01:42:45 +00:00
Makefile Remove NO_WERRORs and WARNS=n's. To be revisited after GCC3. 2002-02-08 23:07:37 +00:00
mkpar.c remove __P 2002-03-22 01:42:45 +00:00
NEW_FEATURES
NOTES
output.c remove __P 2002-03-22 01:42:45 +00:00
reader.c remove __P 2002-03-22 01:42:45 +00:00
README
skeleton.c Style improvements recommended by Bruce as a follow up to some 2001-12-10 21:13:08 +00:00
symtab.c remove __P 2002-03-22 01:42:45 +00:00
verbose.c remove __P 2002-03-22 01:42:45 +00:00
warshall.c remove __P 2002-03-22 01:42:45 +00:00
yacc.1
yyfix.1
yyfix.sh

    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.