* Bob Friesenhahn wrote on Sat, Apr 23, 2005 at 04:36:11PM CEST:
> On Sat, 23 Apr 2005, Ralf Wildenhues wrote:
> >+
> >+8) Note that using libltdl in conjunction with direct uses of dlopening
> >+mechanisms is not supported. For example, it may work if you use
> >+libltdl but another library you use uses dlopen() directly, but it is
> >+unsupported.
>
> What inspired the above? It is normal for there to be multiple users
> of dlopen() in one program. Without it, most programs won't run at
> all. They would not even get off the ground.
Hmm. "It might not do what you want". Sure to be mostly corner cases,
but not impossible: In pseudo code:
Suppose, the module libfoo depends on libbar.
- main calls lt_dlopen("libfoo")
- uses unrelated library libbaz
- libbaz dlopens libbar as well
- main lt_dlclose("libfoo") leads to dlclose(libbar)
- libbaz might still be in use and want to use libbar.
You might argue main should have made libbar resident.
If so, we should mention that in the docs.
Same situation the other way round (lib dlclose()s a module which
libltdl still thinks open).
> The second sentance is not gramatically correct.
I can see that its grammar is terse, but I (seriously!) cannot spot an
error. Gotta ask my girl later, she speaks English better than I do.
But how about this instead:
8) Note that use of libltdl and a native dlopening mechanism for the
same module within one program is not supported.
Regards,
Ralf
