On Tue, Oct 22, 2002 at 01:08:35AM -0400, Ryan Bloom wrote: > If you try to get a value from the table, and the value isn't set, then we > shouldn't return NULL. The fact that we can't determine the difference > between a NULL entry and an unset key is proof that the hash table API is > incorrect. We should fix the API ASAP. I don't see the code in > thread.c, threadpriv.c, and sockets,c that may break. The only place that > those files call these functions is when we are exposing the userdata in > the pool inside the incomplete type.
You didn't answer my question: Why do we _need_ to differenciate between unset and NULL value? Without a specific problem there is no reason to break things. -aaron
