Full_Name: Quanah Gibson-Mount Version: RE24 OS: NA URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (75.111.52.177) ldap_get_dn(3) states that when using the ldap_explode_rdn function, ldap_value_free can be used to free the results. However, ldap_value_free is deprecated. Making things worse, it is suggested that the replacement for ldap_value_free is ldap_value_free_len. ldap_value_free_len expects a bval array, whereas ldap_explode_rdn returns a char* array. Finally, if you look at the actual OpenLDAP library code, what is done there is: vv = ldap_explode_rdn( values[ n ], 0 ); LDAP_VFREE( vv ); where: #define LDAP_VFREE(v) (ber_memvfree_x((void **)(v),NULL)) so NEITHER ldap_value_free NOR ldap_value_free_len are even used when using the ldap_explode_rdn function.
moved from Incoming to Documentation
--On Wednesday, April 22, 2015 11:33 PM +0000 quanah@openldap.org wrote: > Full_Name: Quanah Gibson-Mount > Version: RE24 > OS: NA > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (75.111.52.177) > > > ldap_get_dn(3) states that when using the ldap_explode_rdn function, > ldap_value_free can be used to free the results. However, > ldap_value_free is deprecated. According to *some* of the code, ldap_explode_rdn is actually deprecated: ldap_explode_rdn LDAP_P(( /* deprecated, ldap_str2rdn */ However, it is not wrapped in an ifdef for deprecated, nor is it listed as such in the manpage. --Quanah -- Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration
Need clarification on whether or not some of these functions are deprecated, which is a code issue. Documentation cannot be updated until our code is consistent.
Need to cross reference if they are deprecated in the LDAP v3 RFC, and whether or not the alternatives are usable.
See c7338f5cdd for history of this.