git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carlo Arenas <carenas@gmail.com>
To: "René Scharfe" <l.s.r@web.de>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>,
	git@vger.kernel.org, "Jeff King" <peff@peff.net>,
	"Phillip Wood" <phillip.wood123@gmail.com>,
	"Eric Wong" <e@80x24.org>
Subject: Re: cb/pedantic-build-for-developers, POSIX-but-not-C99 and -Wno-pedantic-ms-format
Date: Tue, 21 Sep 2021 03:48:08 -0700	[thread overview]
Message-ID: <CAPUEsphVKAVvcNvRPBM+8LWRdKq-hmPPSCPx+sAaF1Po7kvxRg@mail.gmail.com> (raw)
In-Reply-To: <b0eba1c6-5468-df31-db6f-701bcd24adff@web.de>

> Right, Microsoft doesn't mention it in its printf format documentation
> [1].  The gettext documentation [3] claims that such platforms get
> replacement functions automatically via libintl.h.

Interesting; Microsoft do provide[1] replacement functions (ending in
_p), but a plain printf won't work.

Carlo

[1] https://docs.microsoft.com/en-us/cpp/c-runtime-library/printf-p-positional-parameters?view=msvc-160

  reply	other threads:[~2021-09-21 10:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-21  0:02 What's cooking in git.git (Sep 2021, #06; Mon, 20) Junio C Hamano
2021-09-21  1:16 ` Junio C Hamano
2021-09-21  3:22 ` Taylor Blau
2021-09-21  8:44 ` cb/pedantic-build-for-developers, POSIX-but-not-C99 and -Wno-pedantic-ms-format Ævar Arnfjörð Bjarmason
2021-09-21 10:10   ` Carlo Arenas
2021-09-21 10:30     ` René Scharfe
2021-09-21 10:48       ` Carlo Arenas [this message]
2021-09-22 16:15       ` Junio C Hamano
2021-09-22 16:58         ` René Scharfe
2021-09-22 16:13   ` Junio C Hamano
2021-09-22 16:25     ` Randall S. Becker
2021-09-22 17:22     ` Randall S. Becker
2021-09-22 17:38     ` Randall S. Becker
2021-09-21 23:07 ` What's cooking in git.git (Sep 2021, #06; Mon, 20) Ævar Arnfjörð Bjarmason
2021-09-23 16:36   ` Junio C Hamano
2021-09-23 16:51     ` Ævar Arnfjörð Bjarmason
2021-09-23 17:41       ` Jeff King
2021-09-22  0:22 ` ns/batched-fsync (was Re: What's cooking in git.git (Sep 2021, #06; Mon, 20)) Ævar Arnfjörð Bjarmason

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=CAPUEsphVKAVvcNvRPBM+8LWRdKq-hmPPSCPx+sAaF1Po7kvxRg@mail.gmail.com \
    --to=carenas@gmail.com \
    --cc=avarab@gmail.com \
    --cc=e@80x24.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=l.s.r@web.de \
    --cc=peff@peff.net \
    --cc=phillip.wood123@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).