On Wed, Mar 20, 2002 at 11:53:09AM -0800, Phil Nelson wrote:
The program I'm porting needs fast access to huge dictionaries, and not so much relational acces. So I thought I'd better use (G)DB. I asked for Berkeley because I read that GDB isn't supported anymore, that aside it would be fine too, and given an existing gpc interface module even a clear favourite.
I think you want to talk about GDBM. GDB is the GNU debugger. GDBM
Yep, stupid mistake.
is the GNU database manager. GDBM still has a maintainer. Not much work has been done on it recently partly due to the fact it works resonably.
I didn't look into it, just believed what the Debian maintainer wrote:
======> Docstring in Deb package <=============== This library is no longer supported by the FSF, and hasn't been worked on in several years -- for new applications, please consider libdb instead, and also consider migrating old applications, see /usr/doc/libgdbmg1-dev/MIGRATE.
======> /usr/doc/libgdbmg1-dev/MIGRATE.gz <====== libgdbm hasn't been maintained, and gnulibc2 has libdb included in it as the dbm-interface replacement. If you've used dbm* interfaces in your code, translation should be easy -- just stop linking with -lgdbm, -lndbm or -ldbm, and link with -ldb instead. ... _Mark_ eichin@kitten.gen.ma.us The Herd of Kittens Ex-Debian GDBM Library Maintainer 1997/6/17
Maybe things have changed since 1997, or this was never true to begin with. Anyhow, I'm not for or against gdbm, just looking for an easy way to get things going. And the portability issue is not relevant *at the moment*, but that has been the case before with this program, hence my problems porting it:)