git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik Faye-Lund <kusmabite@googlemail.com>
To: Julian Phillips <julian@quantumfyre.co.uk>
Cc: git <git@vger.kernel.org>, Eric Raymond <esr@thyrsus.com>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [RFC/PATCH 1/3] strbuf: Add strbuf_vaddf function
Date: Sun, 11 Apr 2010 14:42:29 +0200	[thread overview]
Message-ID: <n2i40aa078e1004110542kcfba8b6dw8848cd8f5647fda7@mail.gmail.com> (raw)
In-Reply-To: <20100411113733.80010.78232.julian@quantumfyre.co.uk>

On Sun, Apr 11, 2010 at 1:37 PM, Julian Phillips
<julian@quantumfyre.co.uk> wrote:
> Add strbuf_vaddf which is to strbuf_addf as vprintf is to printf.
>
> Signed-off-by: Julian Phillips <julian@quantumfyre.co.uk>
> ---
>  strbuf.c |   13 +++++++++++--
>  strbuf.h |    1 +
>  2 files changed, 12 insertions(+), 2 deletions(-)
>
> diff --git a/strbuf.c b/strbuf.c
> index bc3a080..8f312f8 100644
> --- a/strbuf.c
> +++ b/strbuf.c
> @@ -194,19 +194,28 @@ void strbuf_adddup(struct strbuf *sb, size_t pos, size_t len)
>
>  void strbuf_addf(struct strbuf *sb, const char *fmt, ...)
>  {
> +       va_list ap;
> +
> +       va_start(ap, fmt);
> +        strbuf_vaddf(sb, fmt, ap);
> +       va_end(ap);
> +}
> +
> +void strbuf_vaddf(struct strbuf *sb, const char *fmt, va_list args)
> +{
>        int len;
>        va_list ap;
>
>        if (!strbuf_avail(sb))
>                strbuf_grow(sb, 64);
> -       va_start(ap, fmt);
> +       va_copy(ap, args);

Isn't va_copy C99? The only other place we use this is in
compat/winansi.c, but that file is only compiled on Windows. Both
compilers we support on Windows supports va_copy (or some way of
emulating it).

IIRC, strbuf_vaddf() has been attempted added multiple times before
(by me, for one), and the efforts have always ended up being scrapped
due to the lack of a portable va_copy.

-- 
Erik "kusma" Faye-Lund

  reply	other threads:[~2010-04-11 12:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-11 11:37 [RFC/PATCH 0/3] JSON/XML output for scripting interface Julian Phillips
2010-04-11 11:37 ` [RFC/PATCH 1/3] strbuf: Add strbuf_vaddf function Julian Phillips
2010-04-11 12:42   ` Erik Faye-Lund [this message]
2010-04-11 12:59     ` Julian Phillips
2010-04-11 11:37 ` [RFC/PATCH 2/3] add a library of code for producing structured output Julian Phillips
2010-04-11 12:51   ` Erik Faye-Lund
2010-04-11 13:03     ` Julian Phillips
2010-04-11 15:46   ` Jakub Narebski
2010-04-11 18:16   ` Junio C Hamano
2010-04-11 18:26     ` Sverre Rabbelier
2010-04-11 19:21     ` Julian Phillips
2010-04-11 20:34       ` Jakub Narebski
2010-04-11 20:46         ` Julian Phillips
2010-04-11 20:57           ` Eric Raymond
2010-04-11 11:37 ` [RFC/PATCH 3/3] status: add support for " Julian Phillips
2010-04-11 15:48 ` [RFC/PATCH 0/3] JSON/XML output for scripting interface Sverre Rabbelier
2010-04-11 17:30   ` Julian Phillips
2010-04-11 17:34     ` Sverre Rabbelier
2010-04-11 17:45       ` Julian Phillips
2010-04-11 17:50         ` Sverre Rabbelier
2010-04-11 22:22           ` Jon Seymour
2010-04-11 22:34             ` Eric Raymond
2010-04-11 23:25             ` Jon Seymour
2010-04-11 23:30               ` Julian Phillips

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=n2i40aa078e1004110542kcfba8b6dw8848cd8f5647fda7@mail.gmail.com \
    --to=kusmabite@googlemail.com \
    --cc=esr@thyrsus.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=julian@quantumfyre.co.uk \
    --cc=kusmabite@gmail.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 NNTP newsgroup(s).