public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Brett Viren <bv@bnl.gov>
To: Jost Boekemeier <jostobfe@calvados.zrz.TU-Berlin.DE>
Cc: guile-gtk@sourceware.cygnus.com
Subject: Re: Patch to make guile-gtk work with upcoming guile-1.4
Date: Tue, 20 Jun 2000 09:22:00 -0000	[thread overview]
Message-ID: <14671.39420.356715.319254@bnlku15.phy.bnl.gov> (raw)
In-Reply-To: <p2t3dm8fhyx.fsf@himbeere.zrz.tu-berlin.de>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 586 bytes --]

Jost Boekemeier writes:
 > 
 > > when the common usage suggests the _mfpe interface that permits
 > 
 > What does "mfpe" mean and what does the function do that others don´t?
 > Just curious, I don´t have access to the guile sources from here and 
 > I can´t deduce the meaning from the discussion so far.

Mark Free Print Equalp

You use the _mfpe function to tell guile what 4 functions it must call
in order to garbage collect your smob.

See the ``data-rep.info'' page in guile-core/doc for details (get the
CVS version as there has been some changes from 1.3.4).

-Brett.

  reply	other threads:[~2000-06-20  9:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-01 21:05 guile-gtk 0.18 Released Ariel Rios
2000-06-18 19:06 ` Patch to make guile-gtk work with upcoming guile-1.4 Greg J. Badros
2000-06-19  2:06   ` Mikael Djurfeldt
2000-06-19 14:11     ` Greg J. Badros
2000-06-19 15:47       ` Mikael Djurfeldt
2000-06-19 14:49     ` Marius Vollmer
2000-06-19 15:01       ` Greg J. Badros
2000-06-19 21:54         ` Jim Blandy
2000-06-20  8:41           ` Greg J. Badros
2000-06-20  9:15             ` Jost Boekemeier
2000-06-20  9:22               ` Brett Viren [this message]
2000-06-19 14:49   ` Marius Vollmer

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=14671.39420.356715.319254@bnlku15.phy.bnl.gov \
    --to=bv@bnl.gov \
    --cc=guile-gtk@sourceware.cygnus.com \
    --cc=jostobfe@calvados.zrz.TU-Berlin.DE \
    /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).