LALR(1) parser generator

Edit Package byacc
http://invisible-island.net/byacc/byacc.html

Berkeley Yacc is a LALR(1) parser generator. It has been made as compatible as
possible with AT&T Yacc and it accepts any input specification that conforms to
the AT&T Yacc documentation. In contrast to bison, it is written to avoid
dependencies upon a particular compiler.

Refresh
Refresh
Source Files
Filename Size Changed
byacc-20141006.tgz 0000709685 693 KB
byacc.changes 0000005034 4.92 KB
byacc.spec 0000001868 1.82 KB
Revision 14 (latest revision is 35)
Stephan Kulow's avatar Stephan Kulow (coolo) accepted request 254941 from Guido Berhoerster's avatar Guido Berhoerster (gberh) (revision 14)
- update to version 20141006
  - package/debian/source/format: change to native format to work
    around regression in Debian packaging.
  - main.c: correct parameter for umask - for very old mkstemp's -
    and use type mode_t to quiet compiler warning
  - configure.in: add configure check for mode_t
  - reader.c: better fix for get_line, by ensuring there is enough
    space to null-terminate its result (prompted by discussion with
    Craig Rodrigues).
  - main.c: make change to umask before calling mkstemp, as
    suggested in Coverity #56902
  - reader.c: adjust logic in copy_action to avoid potential
    null-pointer dereference (Coverity #56901)
  - reader.c: adjust logic to avoid potential null-pointer
    dereference in compile_args (Coverity #63407)
  - reader.c: eliminate strcpy into fixed-size buffer (Coverity
    #63408)
  - yacc.1: document changes made with respect to %parse-param
  - output.c: add parameters from %parse-param to destructor.  The
    order of the parameters is intentionally inconsistent with
    yyparse/yyerror, for "compatibility" with bison.
  - output.c: use puts_param_types/puts_param_names to output
    lex_param data.
  - btyaccpar.c: add casts, change types to fix strict compiler
    warnings
  - output.c: gcc-warning
  - output.c: fix limit when merging real/workaround tables
  - output.c: for btyacc, it is possible to have no conflicts - but
    in that case, the "ctable" was not generated at all, while the
    skeleton uses the table.  The most straightforward (workaround)
Comments 0
openSUSE Build Service is sponsored by