From: Zeeshan Ali <zeenix@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Module unloading
Date: Fri, 27 May 2005 01:00:41 +0500 [thread overview]
Message-ID: <38294b740505261300324ed650@mail.gmail.com> (raw)
In-Reply-To: <42961684.3000802@ossau.uklinux.net>
Hello,
> Yes. This is covered in general terms by the comments in my earlier
> email today, but for the specific problem you describe, all you need to
> do is:
>
> - export `xchat-register-plugin' from your main infrastructure module,
> which let's say is (xchat main)
>
> - document that plugin authors need to write `(use-modules (xchat
> main))' at the start of their plugin code.
Yes, Rob suggested this method on IRC this evening, but it seems to
further complicate the maters as i was trying to unref one module
reference and this way i'll get two to worry about.
One thing that i found out is that module can't really be
unloaded. E.g if i load a module (either using use-modules or
resolve-module), unload/unuse it (using the code you showed me), edit
the module and then load it again, i don't get my changes; instead the
same old version of module get's loaded, which means the module didn't
get unloaded.
Regards,
Zeeshan Ali
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2005-05-26 20:00 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 [this message]
2005-05-26 18:25 ` Neil Jerram
2005-05-26 19:45 ` Zeeshan Ali
2005-05-24 21:14 ` Rob Browning
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=38294b740505261300324ed650@mail.gmail.com \
--to=zeenix@gmail.com \
--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).