John Darrington <[EMAIL PROTECTED]> writes: > Would it be a good idea to have a version of hash.c which uses a pool > to do its memory allocation?
Yes, that's a good idea. I'd suggest just adding a pool parameter to the existing hash_create function, then changing the *malloc and free calls to pool_* and pool_free calls. Callers who don't want a pool can just pass a null pointer, because pool_*malloc and pool_free interpret a null pointer as a request to just call malloc or free. -- "Platonically Evil Monkey has been symbolically representing the darkest fears of humanity since the dawn of literature and religion, and I think I speak for everyone when I give it a sidelong glance of uneasy recognition this evening." --Scrymarch _______________________________________________ pspp-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/pspp-dev
