From: Andy Wingo <wingo@pobox.com>
To: Doug Evans <xdje42@gmail.com>
Cc: Mark H Weaver <mhw@netris.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: RFC: Foreign objects facility
Date: Tue, 29 Apr 2014 20:27:20 +0200 [thread overview]
Message-ID: <87d2g0uh2v.fsf@pobox.com> (raw)
In-Reply-To: <CAP9bCMQFiQr789eQVfq5JEQbZFtpPju2t5uhExE98vbD9L0hMQ@mail.gmail.com> (Doug Evans's message of "Tue, 29 Apr 2014 09:08:54 -0700")
Hi!
On Tue 29 Apr 2014 18:08, Doug Evans <xdje42@gmail.com> writes:
> Hi. fwiw, this is all great stuff (and welcome!), but I think it's in
> the wrong place in the docs.
> The issue comes up in multiple places, so I would write it ("it" being
> the general prose regarding issues with finalizers) once and refer to
> it from all the places that use finalizers.
> That would make this section shorter (more likely to be read) and
> *everywhere* that has to deal with finalizers benefits from far more
> easily finding all this great text.
Perhaps this text fragment was misinterpreted; the stable-2.0 docs have
been updated in git to the same thing, but the master HTML docs have
been pushed to the web site. Note that in:
http://www.gnu.org/software/guile/docs/master/guile.html/Programming-in-C.html#Programming-in-C
I've removed the tutorial-like section on smobs, and that later in the
API reference the SMOB documentation links to "Foreign Object Memory
Management" when discussing the pitfalls of finalizers.
Does that cover your needs?
A
--
http://wingolog.org/
next prev parent reply other threads:[~2014-04-29 18:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-27 13:17 RFC: Foreign objects facility Andy Wingo
2014-04-27 16:00 ` Mark H Weaver
2014-04-27 16:46 ` Stefan Israelsson Tampe
2014-04-28 17:47 ` Andy Wingo
2014-04-27 17:51 ` Andy Wingo
2014-05-03 4:57 ` Doug Evans
2014-04-28 16:08 ` Andy Wingo
2014-04-29 16:08 ` Doug Evans
2014-04-29 18:27 ` Andy Wingo [this message]
2014-04-28 8:24 ` Ludovic Courtès
2014-04-28 18:05 ` Andy Wingo
2014-04-29 15:56 ` Doug Evans
2014-04-29 18:25 ` Andy Wingo
2014-05-03 5:45 ` Doug Evans
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=87d2g0uh2v.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
--cc=xdje42@gmail.com \
/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).