From: Noah Lavine <noah.b.lavine@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: Guile Mailing List <guile-user@gnu.org>
Subject: Re: on coding a portable R6RS package supporting Guile and its FFI
Date: Tue, 5 Feb 2013 14:29:38 -0500 [thread overview]
Message-ID: <CA+U71=NCs-TFuO7qCvC8vnnr396p8iHyp8qYFjjuJrVU4oewWg@mail.gmail.com> (raw)
In-Reply-To: <87sj5afyos.fsf@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
Hello,
That does sound very useful. The only thing that makes me worried is
On Tue, Feb 5, 2013 at 12:38 PM, Andy Wingo <wingo@pobox.com> wrote:
> On Thu 17 Jan 2013 11:53, Marco Maggi <marco.maggi-ipsu@poste.it> writes:
> > The other Scheme implementations using a non-compacting
> > garbage collector
>
Do we want to guarantee that our garbage collector will always be
non-compacting, or force major interface changes if it is? (I realize we've
already taken out smob mark procedures, but this is in some ways even
harder to add back.)
I'm not sure this is a big deal, but maybe we should consider what would
happen in the future if we did want to change. Using bytevector->pointer is
an acceptable cost to pay for flexibility, IMHO.
Noah
[-- Attachment #2: Type: text/html, Size: 1340 bytes --]
next prev parent reply other threads:[~2013-02-05 19:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 10:53 on coding a portable R6RS package supporting Guile and its FFI Marco Maggi
2013-01-27 15:08 ` Ludovic Courtès
2013-01-28 3:00 ` Daniel Hartwig
2013-02-05 17:38 ` Andy Wingo
2013-02-05 19:29 ` Noah Lavine [this message]
2013-02-06 8:36 ` Andy Wingo
2013-02-06 13:25 ` Noah Lavine
2013-02-05 22:31 ` Ludovic Courtès
2013-02-06 10:57 ` Andy Wingo
2013-02-08 14:10 ` Ludovic Courtès
2013-02-08 14:37 ` Andy Wingo
2013-02-08 15:52 ` 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='CA+U71=NCs-TFuO7qCvC8vnnr396p8iHyp8qYFjjuJrVU4oewWg@mail.gmail.com' \
--to=noah.b.lavine@gmail.com \
--cc=guile-user@gnu.org \
--cc=wingo@pobox.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).