unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Passing C pointers through guile
Date: Thu, 10 Jul 2008 15:01:51 +0200	[thread overview]
Message-ID: <874p6xx58g.fsf@gnu.org> (raw)
In-Reply-To: Pine.LNX.4.64.0807101442540.5265@ttleush

Hi,

"Kjetil S. Matheussen" <k.s.matheussen@notam02.no> writes:

> Point is that you very often don't need any kind of free functionality.
> For example, if you create a gui widget, you probably have a callback
> function which is called if the gui is closed. That callback
> function can free any allocated memory. Another example from snd
> is creating ladspa plugins (audio plugins in linux). Handlers
> from those, plus variuos configuration stuff, is alive througout
> the whole session and will be automatically freed when the program
> closes.

Sure, but the general case is that a C-implemented object must be
explicitly destroyed when it's no longer referenced by Scheme code.

Thanks,
Ludovic.





  reply	other threads:[~2008-07-10 13:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-10 12:49 Passing C pointers through guile Kjetil S. Matheussen
2008-07-10 13:01 ` Ludovic Courtès [this message]
     [not found] <cmu-lmtpd-26382-1215792388-9@mail-imap1.uio.no>
2008-07-11 17:22 ` Kjetil S. Matheussen
  -- strict thread matches above, loose matches on Subject: below --
2008-07-09 20:09 Kjetil S. Matheussen
2008-07-09 20:43 ` Ludovic Courtès
2008-07-11 13:05 ` Greg Troxel
2008-07-11 13:12   ` Kjetil S. Matheussen
2008-07-11 14:42     ` Ludovic Courtès
2008-07-09 19:58 Kjetil S. Matheussen
     [not found] <cmu-lmtpd-29205-1215446748-1@mail-imap1.uio.no>
2008-07-09 16:50 ` Kjetil S. Matheussen
2008-07-09 18:32   ` Kjetil S. Matheussen
2008-07-09 19:37     ` Ludovic Courtès
2008-07-09 19:35   ` Ludovic Courtès

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=874p6xx58g.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@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).