From: Mark H Weaver <mhw@netris.org>
To: guile-devel@gnu.org
Subject: Re: [PATCH] Implement scm_call_varargs and scm_call_{7,8,9}
Date: Mon, 30 Jan 2012 11:20:08 -0500 [thread overview]
Message-ID: <87aa55i2mf.fsf@netris.org> (raw)
In-Reply-To: <877h09z07g.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 30 Jan 2012 16:20:19 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> 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.)
Excellent suggestion! 'scm_call' it is :)
Thanks,
Mark
prev parent reply other threads:[~2012-01-30 16: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
2012-01-30 16:20 ` Mark H Weaver [this message]
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=87aa55i2mf.fsf@netris.org \
--to=mhw@netris.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).