[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lt_dlopenall patch
From: |
Alexandre Oliva |
Subject: |
Re: lt_dlopenall patch |
Date: |
08 Jun 2001 04:55:50 -0300 |
User-agent: |
Gnus/5.090003 (Oort Gnus v0.03) XEmacs/21.4 (Academic Rigor) |
On Jun 7, 2001, "Gary V. Vaughan" <address@hidden> wrote:
> It adds a new function lt_dlopenall, which runs a client
> supplied callback function for each file it has successfully lt_dlopened.
Methinks it would be nice if another callback were called before
attempting to dlopen a module, that could tell lt_dlopenall not to
dlopen that particular module.
I find it a bit dangerous to go dlopening modules at random, just
because they are in the search path. Think of modules whose
dynamic initializers do something odd, such as open a window or start
a new thread to do some monitoring, whatever.
In fact, I'd go a step further and, instead of lt_dlopenall, I'd
introduce lt_dlfindmodules(process_module_fn, extra_arg), so that
process_module_fn would be called for each module *found*, so that it
could decide beforehand whether to lt_dlopen it or not. It could also
add it to a list in extra_arg, then present the list of modules found
to the user, that could decide which modules to dlopen.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer address@hidden, redhat.com}
CS PhD student at IC-Unicamp address@hidden, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
- lt_dlopenall patch, Gary V . Vaughan, 2001/06/07
- Re: lt_dlopenall patch,
Alexandre Oliva <=