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: Merging ‘bdw-gc-static-alloc’
Date: Fri, 23 Oct 2009 14:57:25 +0200	[thread overview]
Message-ID: <m3bpjynu8a.fsf@pobox.com> (raw)
In-Reply-To: <87vdi6sc5m.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 23 Oct 2009 11:16:37 +0200")

EHLO

On Fri 23 Oct 2009 11:16, ludo@gnu.org (Ludovic Courtès) writes:

> Andy Wingo <wingo@pobox.com> writes:
>
>> On Fri 02 Oct 2009 02:15, ludo@gnu.org (Ludovic Courtès) writes:
>>
>>> Because of the macrology that’s used to statically allocate stringbufs [0],
>>> the string has to be a literal:
>>>
>>>   SCM_SYMBOL (s_foo, "foo");
>>>
>>> What do you think?
>>
>> Need more information :) How widespread is the non-literal usage? Could
>> you grep the source packages of the Guile users that you have identified
>> for occurrences of this idiom?
>
> Apparently this is going to be rare.  I’ve found no occurrences here:
>
> So I’d be tempted to merge this in.
>
> What do you think?

Roll on, merge train, roll on!

I have finished case-lambda, but am rebasing and cleaning up patches I
haven't pushed yet. So it's a race. Gentlemen, start your git rebase &
push!

A
-- 
http://wingolog.org/




  reply	other threads:[~2009-10-23 12:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02  9:15 Merging ‘bdw-gc-static-alloc’ Ludovic Courtès
2009-10-02 16:26 ` Andy Wingo
2009-10-23  9:16   ` Ludovic Courtès
2009-10-23 12:57     ` Andy Wingo [this message]
2009-11-02 21:44       ` Ludovic Courtès
2009-11-03 20:57         ` (no subject) Neil Jerram
2009-11-05 22:30           ` Merging ‘bdw-gc-static-alloc’ Ludovic Courtès
2009-11-08 22:21             ` (no subject) Neil Jerram

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=m3bpjynu8a.fsf@pobox.com \
    --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).