unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Brad Medeiros <bradmedeiros0@gmail.com>
To: guile-user@gnu.org
Subject: Deleting a Module
Date: Mon, 11 Oct 2021 00:25:14 -0700	[thread overview]
Message-ID: <CAMnXraRC_CtZqtvsBzYKXS=LoPZnjg7dXnA405qSCBwFOCbgAw@mail.gmail.com> (raw)

Hi Everyone!

I currently use guile's module system for a scripting plugin style system,
where these plugins should get loaded and unloaded fairly often.

After profiling my code, I realize that I'm leaking memory, and I'm pretty
sure it's because the modules I've created never get cleaned up.

I create the modules with scm_c_define_module, but is there functionality
that can be used as the equivalent of what would be a
corresponding scm_c_undefine_module, or even something like a reload that I
could use to create a pool of modules to reuse?

Thanks!


                 reply	other threads:[~2021-10-11  7:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAMnXraRC_CtZqtvsBzYKXS=LoPZnjg7dXnA405qSCBwFOCbgAw@mail.gmail.com' \
    --to=bradmedeiros0@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).