punkish-- for not reading the docs carefully.
perrin++ for pointing out the problem, and saving me from committing crimes to my Dell.
DBM::Deep is a great module because of its portability. It has two problems for now that prevent me from using it. I was unable to install it cleanly on my Mac (I think Module::Build was causing it to throw up). But, really, DBM::Deep is way too slow for some of the functions I need. Once I figure out a way around those, I will look back at DBM::Deep, and probably migrate to it.
--
when small people start casting long shadows, it is time to go to bed
| [reply] |
What problems are you having? I'm surprised that it's throwing up on the Mac because I am developing DBM::Deep on a Mac.
What kind of functions are too slow? I'm currently rewriting the engine code from the ground up and would like to know where your speed requirements are.
And, dbm-deep is a great module for another major reason - it's Perl's datastructures tied to disk in a multi-process fashion. This allows you to think in Perl's datastructures without having to worry about how to store stuff until later (if ever).
My criteria for good software:
- Does it work?
- Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
| [reply] |