Why ldap_<first,next>_attribute ?

[Hallvard B Furuseth <h.b.furuseth@usit.uio.no>]

Why has Umich LDAP and ldap-c-api *two* functions
ldap_first/next_attribute to get the attribute list, instead of just
	char **ldap_get_attributes(LDAP *, LDAPMessage *)
which would return a NULL-terminated array of attribute values?
Can unneeded next_attribute take up much resources, or something?
But then, I don't remember ever stopping halfway through an
ldap_first/next_attribute walk anyway.

I'd like to see ldap_get_attributes above in the API.
(Though admittedly it's not that hard to implement it by hand:-)

-- 
Hallvard