[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: ltdl vs. dlfcn & so

Please just use libltdl, that's what it's for - to hide platform
dependencies. Introducing our own set of macros and #ifdef's completely
defeats the purpose.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support

> -----Original Message-----
> From: owner-openldap-devel@OpenLDAP.org
> [mailto:owner-openldap-devel@OpenLDAP.org]On Behalf Of Pierangelo
> Masarati
> Sent: Saturday, November 09, 2002 7:33 AM
> To: openldap-devel@OpenLDAP.org
> Subject: ltdl vs. dlfcn & so
> While playing with SLAPI, I noticed it directly uses
> dlfcn stuff, e.g. #include <dlfcn.h>, dlopen() and so,
> while slapd/module.c uses ltdl stuff.  I understand
> the latter is far more portable (virtually platform
> independent) and much more versatile, but it requires
> another library to be available; to make things uniform
> we might wrap calls in a SLAP_DL*(), or rather
> LDAP_PVT_DL*() fashion and let configure check for libltdl
> and, in case of failure, for libdl with dl*() api
> (and for any other platform specific replacement).
> I'd prefer to have a uniform loadable stuff approach
> throughout the package (e.g. to put everything in libldap
> with a ldap_pvt_*() interface both for SLAPI and modules.
> Comments, before I start coding?
> Pierangelo.
> --
> Dr. Pierangelo Masarati         mailto:pierangelo.masarati@sys-net.it
> LDAP Architect, SysNet s.n.c.   http://www.sys-net.it