Hashtrees a bit unflexible

Andreas Rottmann <[email protected]> Mon, 15 Mar 2004 13:34:39 +0100
Newsgroups gmane.lisp.scheme.pika.devel
Message-ID <[email protected]>
I just noted that hackerlabs hashtrees are a bit unflexible compared
to the GLib ones: You cannot pass an additional pointer to e.g. the
hashtree_free_data_fn. I would however need this functionality to be
able to keep the storage in a memchunk for efficient (esp. space-wise)
allocation. 

A hack to do so would involve using a special "rules" structure that
has an additional field. Is this the way it's ment to work, or should
hashtree functions be extended to take an additional void * argument?
If the argument would be last, this change wouldn't break ABI wrt
existing usage, I think. Tom?

Cheers, Andy
-- 
Andreas Rottmann         | [email protected]      | 118634484@ICQ | [email protected]
http://yi.org/rotty      | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint              | DFB4 4EB4 78A4 5EEE 6219  F228 F92F CFC5 01FD 5B62

The best way to accelerate a Windows machine is at 9.81 m/s^2