Use the more standard files `xalloc.h' and `xmalloc.c' instead of
authorAkim Demaille <akim@epita.fr>
Mon, 2 Oct 2000 08:48:32 +0000 (08:48 +0000)
committerAkim Demaille <akim@epita.fr>
Mon, 2 Oct 2000 08:48:32 +0000 (08:48 +0000)
commitd7913476c462b480f11e14b6829942f2691c6c01
tree9239af2eba1cfc96298883dd5d3756f7e468d606
parent340ef489223a5d1f9c40674ea2973435cb8ecc1b
Use the more standard files `xalloc.h' and `xmalloc.c' instead of
Bison's `allocate.c' and `alloc.h'.  This patch was surprisingly
difficult and introduced a lot of core dump.  It turns out that
Bison used an implementation of `xmalloc' based on `calloc', and
at various places it does depend upon the initialization to 0.  I
have not tried to isolate the pertinent places, and all the former
calls to Bison's `xmalloc' are now using `XCALLOC'.  Someday,
someone should address this issue.
* src/allocate.c, src/alloc.h, m4/bison-decl.m4: Remove.
* lib/xmalloc.c, lib/xalloc.h, m4/malloc.m4, m4/realloc.m4: New
files.
Adjust dependencies.
* src/warshall.h: New file.
Propagate.
28 files changed:
ChangeLog
configure.in
lib/Makefile.am
lib/xalloc.h [new file with mode: 0644]
lib/xmalloc.c [new file with mode: 0644]
m4/Makefile.am
m4/bison-decl.m4
m4/malloc.m4 [new file with mode: 0644]
m4/realloc.m4 [new file with mode: 0644]
src/LR0.c
src/Makefile.am
src/alloc.h
src/allocate.c
src/closure.c
src/conflicts.c
src/derives.c
src/files.c
src/lalr.c
src/lex.c
src/main.c
src/nullable.c
src/output.c
src/print.c
src/reader.c
src/reduce.c
src/symtab.c
src/warshall.c
src/warshall.h [new file with mode: 0644]