From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@pobox.com>
Cc: 10974@debbugs.gnu.org, Alexei Matveev <alexei.matveev@gmail.com>
Subject: bug#10974: guile-user@gnu.org
Date: Tue, 03 Jul 2012 00:35:29 +0200 [thread overview]
Message-ID: <871uktu6z2.fsf@gnu.org> (raw)
In-Reply-To: <87vci5rg54.fsf@pobox.com> (Andy Wingo's message of "Mon, 02 Jul 2012 23:45:43 +0200")
Hi,
Andy Wingo <wingo@pobox.com> skribis:
> Would this be "fixed" if we changed these to be implemented as inline
> functions?
In some way, though their address could still not be taken.
Thanks,
Ludo’.
next prev parent reply other threads:[~2012-07-02 22:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 11:36 bug#10974: guile-user@gnu.org Alexei Matveev
2012-07-02 9:38 ` Ludovic Courtès
2012-07-02 10:15 ` Alexei Matveev
[not found] ` <CACMrLAeaLn4Bw13TitmeAO8sympbsvFRkM+skFrMTvSe0iYf2w@mail.gmail.com>
2012-07-02 19:17 ` Ludovic Courtès
2012-07-02 21:45 ` Andy Wingo
2012-07-02 22:35 ` Ludovic Courtès [this message]
2012-07-02 23:17 ` Andy Wingo
2012-07-03 8:09 ` 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=871uktu6z2.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=10974@debbugs.gnu.org \
--cc=alexei.matveev@gmail.com \
--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).