On Tue, 2009-12-08 at 12:43 -0500, John Dennis wrote:
I think Simo's suggestion of using the delete callback in these cases
is
the best idea. If you allow returning values from the delete
operation
you have the potential for inconsistencies. How do you know if value
returned is still valid after the delete? It might have been freed by
the delete callback. No API changes are necessary and no performance
impacts are encountered if you just use the callback mechanism.
The only problem is that the delete_callback has no context, but this is
a problem I was already seeing in other contexts. I'm preparing a patch
so that the callback can get a private data pointer.
Simo.
--
Simo Sorce * Red Hat, Inc * New York