On Mar 20, 2001, "Gary V. Vaughan" <[EMAIL PROTECTED]> wrote:
>> anyways, in the case such code arrives, it may
>> only be called after successfull g_module_init(). that means for libtool,
>> there must be ways to supress automatic constructor initialization at
>> loading time and do them on demand later on.
> Yikes! I'm Cc:ing the libtool list to record this information for
> posterity, and incase any of the KDE folks that lurk here know
> better than I do :-)
Instead of suppressing automatic constructors, we may just have a
dynamic constructor that sets some global variable to 1, which we test
in module_init() to decide whether dynamic constructors have already
been run.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
_______________________________________________
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool
