Re: Keywords as hash: API design: null or empty hash

Julian Foad wrote:
> Yes. That's why it's a bit of a special case: the concept is not that a
> keywords hash can be null, but that some functions take an _optional_
> keywords hash, and thus accept NULL as the alternative to a keywords
> hash.

OK, that makes perfect sense to me now. There would be nothing gained by
creating a special type that would just alias apr_hash_t (which is what I did in
one of my earlier patches).

Thanks for helping get this into the code (both of you)! Hopefully, I can find
some time to start working on inherited properties, where this code change will
come in very handy.

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org