Re: Add ldif.h to the public headers?

I have no strong opinion about whether they should be folded into 
libldap or kept in a separate library.  I do know that the LDIF 
functions were originally designed for "internal use only" purposes and 
as such the APIs are not very modern or safe.  For example, the caller 
needs to be careful to provide adequately sized buffers and so on.

-Mark


Anton Bobrov wrote:
> i'm definitely not against making them public but my take on it would
> be keeping them in libldif, making libldif available in dist on par
> with other libs ie .so and not .a only and then making ldif.h public.