You're right, it would also be the better alternative. I already did this as a fix in my apps and other hashtable implementations are mostly using this technique too. But I'm not sure of the apr-'policy'. AFAIK public structs are avoided wherever possible in the headers.
Yes, they are avoided, but this might be a case where exposure is warranted.
Since I'm not exactly clear what was suggested, if you could submit a patch that does this (and works for you), it'd be appreciated. -- justin
