tdb2: use separate magic constants for chain, htable and ftable entries
authorRusty Russell <rusty@rustcorp.com.au>
Wed, 1 Dec 2010 13:15:56 +0000 (23:45 +1030)
committerRusty Russell <rusty@rustcorp.com.au>
Wed, 1 Dec 2010 13:15:56 +0000 (23:45 +1030)
commit2491b65a6d10cd6ca1a3e05bf535eb0180047922
tree6420c3e0d4b3204176b6059dc10888710f2162ca
parentf5087965ebdb24618ca59854b7a819e21c9fdf78
tdb2: use separate magic constants for chain, htable and ftable entries

Rather than overloading TDB_USED_MAGIC and the hash value as we do now.
We also rename "free list" to the more-accurate "free table" everywhere.
14 files changed:
ccan/tdb2/check.c
ccan/tdb2/free.c
ccan/tdb2/hash.c
ccan/tdb2/lock.c
ccan/tdb2/private.h
ccan/tdb2/summary.c
ccan/tdb2/tdb.c
ccan/tdb2/test/layout.c
ccan/tdb2/test/layout.h
ccan/tdb2/test/run-001-encode.c
ccan/tdb2/test/run-03-coalesce.c
ccan/tdb2/test/run-04-basichash.c
ccan/tdb2/test/run-30-exhaust-before-expand.c
ccan/tdb2/test/run-50-multiple-freelists.c