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: Fri, 25 Mar 2011 19:44:04 +0100 [thread overview]
Message-ID: <m37hbnf3bf.fsf@unquote.localdomain> (raw)
In-Reply-To: <87hbardqgw.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 25 Mar 2011 19:06:55 +0100")
Hi,
On Fri 25 Mar 2011 19:06, ludo@gnu.org (Ludovic Courtès) writes:
> Andy Wingo <wingo@pobox.com> writes:
>
>> I think we made a mistake in exposing bdw-gc.h to libguile.h users.
>> gc.h is quite scrupulous to not include it, but smob.h, inline.h
>> (sometimes), and pthread-threads.h pull it in.
>
> <libguile/bdw-gc.h> is intentionally pulled because our public headers
> use macros and inlines from <gc/gc.h>.
Right; I think this is a mistake, because it couples our external
interface too tightly to libgc's interface.
>> I think that in 2.2 we should not expose libgc interfaces in libguile,
>
> That would be great, but then ‘scm_cell’, ‘SCM_NEWSMOB’, etc. would
> need to do a function call, which we don’t want. Even if we did want
> it, the change would break the ABI.
I realize this :) That's why I am proposing it for 2.2, which will
(presumably) be ABI-incompatible. I don't think inlining NEWSMOB et al
actually buys us anything worth buying, so to speak.
>> and that in 2.0 we should disable pthread redirects.
>
> Why?
I think I addressed this in my other mail; perhaps we can continue the
discussion there.
> 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
Regards,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-03-25 18:44 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 [this message]
2011-03-27 15:11 ` Ludovic Courtès
2011-03-28 7:35 ` Andy Wingo
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=m37hbnf3bf.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).