unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: bdw-gc includes in libguile.h
Date: Mon, 28 Mar 2011 09:35:02 +0200	[thread overview]
Message-ID: <m3r59rbsux.fsf@unquote.localdomain> (raw)
In-Reply-To: <874o6ovbsa.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 27 Mar 2011 17:11:17 +0200")

Greets :)

On Sun 27 Mar 2011 17:11, ludo@gnu.org (Ludovic Courtès) writes:

> Internally we should still inline scm_cell & co., though; that can be
> done without exposing <gc/gc.h> in public headers I guess.  (Actually,
> we should inline scm_cons, too, internally.)

Agreed.

>>> A meta-comment: can we agree to take more time to discuss this sort of
>>> things?  I’ll try to be responsive, and the earth won’t stop spinning if
>>> the fix waits a couple of days.  ;-)
>>
>> Sure.  Sorry for the precipitous action.  That said, this bug has been
>> open since September:  https://savannah.gnu.org/bugs/?32436
>
> Oh indeed, I hadn’t realized there’s a connection; still...

Do you have any thoughts on that bug, or the recent threads.c patches?

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2011-03-28  7:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-25  9:38 bdw-gc includes in libguile.h Andy Wingo
2011-03-25 16:44 ` Andy Wingo
2011-03-25 18:06 ` Ludovic Courtès
2011-03-25 18:44   ` Andy Wingo
2011-03-27 15:11     ` Ludovic Courtès
2011-03-28  7:35       ` Andy Wingo [this message]
2011-03-28 19:22         ` Ludovic Courtès
2011-03-28 19:41           ` Andy Wingo
2011-03-28 20:40             ` Ludovic Courtès
2011-03-29  9:16               ` Andy Wingo
2011-03-30 16:15                 ` Ludovic Courtès
2011-03-30 16:23                   ` Andy Wingo
2011-05-26 16:48     ` Andy Wingo

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=m3r59rbsux.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).