From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: [PATCH] Implement scm_call_varargs and scm_call_{7,8,9}
Date: Mon, 30 Jan 2012 16:20:19 +0100 [thread overview]
Message-ID: <877h09z07g.fsf@gnu.org> (raw)
In-Reply-To: 874nvdxxpl.fsf@pobox.com
Andy Wingo <wingo@pobox.com> skribis:
> On Mon 30 Jan 2012 02:04, Mark H Weaver <mhw@netris.org> writes:
>
>> Andy suggested that we should add these, so here's a patch to do so.
>> Okay to push?
>
> Looks great to me, thanks. Please push.
Can we s/scm_call_varargs/scm_call/ instead? (For consistency with
scm_list_n, it would be ‘scm_call_n’, but that one is already taken for
something else.)
Other than that, OK!
Thanks,
Ludo’.
next prev parent reply other threads:[~2012-01-30 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 1:04 [PATCH] Implement scm_call_varargs and scm_call_{7,8,9} Mark H Weaver
2012-01-30 10:59 ` Andy Wingo
2012-01-30 15:20 ` Ludovic Courtès [this message]
2012-01-30 16:20 ` Mark H Weaver
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=877h09z07g.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).