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: Why bother porting Guile to BDW-GC?
Date: Tue, 11 Nov 2008 21:11:01 +0100	[thread overview]
Message-ID: <87skpyrpka.fsf@gnu.org> (raw)
In-Reply-To: 49dd78620811101257p7eb949e7t47042347f81249eb@mail.gmail.com

Hi Neil!

"Neil Jerram" <neiljerram@googlemail.com> writes:

> This all sounds pretty compelling to me.  From my point of view, you
> and Han-Wen have the most knowledge of this area, and Han-Wen has one
> of the most demanding applications - so if you and Han-Wen are happy
> to go ahead, I'm happy too.

Great.  I hope others view these arguments as compelling, too.

> Just in case some really hard problem emerges, is it possible to
> organize the development so that we could retain the option for a
> while - say, a few months - to switch back?

I think the best we can do is keep the thing in a separate branch.  It's
already too late to have, say, a configure-time option to choose GCs
(because I did not plan to do this when I started).  It would have been
quite hard anyway since the current GC code is quite entangled with the
rest of Guile in some places.

Does that seem like a reasonable plan?

Thanks,
Ludo'.





  reply	other threads:[~2008-11-11 20:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-08 15:58 Why bother porting Guile to BDW-GC? Ludovic Courtès
2008-11-09  2:23 ` Han-Wen Nienhuys
2008-11-09  2:27   ` Han-Wen Nienhuys
2008-11-09 18:25   ` Ludovic Courtès
2008-11-10 20:57 ` Neil Jerram
2008-11-11 20:11   ` Ludovic Courtès [this message]
2008-11-11 20:32     ` Andy Wingo
2008-11-12  8:28       ` Ludovic Courtès
2008-11-10 21:10 ` Ludovic Courtès
2008-11-11 20:42 ` 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=87skpyrpka.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).