From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-user@gnu.org
Subject: Re: Module unloading
Date: Tue, 24 May 2005 16:14:18 -0500 [thread overview]
Message-ID: <87r7fwmimt.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <42936F3C.3090409@ossau.uklinux.net> (Neil Jerram's message of "Tue, 24 May 2005 19:15:24 +0100")
Neil Jerram <neil@ossau.uklinux.net> writes:
> This way there is no magic, and the visibility of the plugin bindings
> is under the control of the plugin author. Also, this way you could
> stay pure-R5RS if you like, as you don't really need any features of
> the module system.
This made me wonder -- what happens if you dynamically load (dlopen) a
lib that depends on libguile, and then you later dlclose that lib?
What happens to libguile? Presumably it will be unloaded too. Does
Guile tolerate that?
If so, does Guile tolerate being re-loaded? For example if you then
re-dlopen the lib that depends on libguile and start using it?
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2005-05-24 21:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 14:03 Module unloading Zeeshan Ali
2005-05-23 18:18 ` Neil Jerram
2005-05-23 20:55 ` Zeeshan Ali
2005-05-23 21:23 ` Neil Jerram
2005-05-24 13:02 ` Zeeshan Ali
2005-05-24 18:15 ` Neil Jerram
2005-05-24 21:06 ` Zeeshan Ali
2005-05-24 21:26 ` Zeeshan Ali
2005-05-26 12:16 ` Zeeshan Ali
2005-05-26 18:33 ` Neil Jerram
2005-05-26 20:00 ` Zeeshan Ali
2005-05-26 18:25 ` Neil Jerram
2005-05-26 19:45 ` Zeeshan Ali
2005-05-24 21:14 ` Rob Browning [this message]
2005-05-26 18:43 ` Neil Jerram
2005-05-26 18:57 ` Rob Browning
2005-05-26 19:05 ` Neil Jerram
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r7fwmimt.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).