From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-compat-util: always enable variadic macros
Date: Wed, 27 Jan 2021 22:13:29 -0800 [thread overview]
Message-ID: <xmqq5z3hy4fq.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <YBJLgY+CWtS9TeVb@coredump.intra.peff.net> (Jeff King's message of "Thu, 28 Jan 2021 00:28:33 -0500")
Jeff King <peff@peff.net> writes:
> We allow variadic macros in the code base, but only if there is fallback
> code for platforms that lack it. This leads to some annoyances:
>
> - the code is more complicated because of the fallbacks (e.g.,
> trace_printf(), etc, is implemented twice with a set of parallel
> wrappers).
>
> - some constructs are just impossible and we've had to live without
> them (e.g., a cross between FLEX_ALLOC and xstrfmt)
>
> Since this feature is present in C99, we may be able to start counting
> on it being available everywhere. Let's start with a weather balloon
> patch to find out.
>
> This patch makes the absolute minimal change by always setting
> HAVE_VARIADIC_MACROS. If somebody runs into a platform where it's a
> problem, they can undo it by commenting out the define. Likewise, if we
> have to revert this, it would be quite unlikely to cause conflicts.
>
> Once we feel comfortable that this is the right direction, then we can
> start ripping out all the spots that actually look at the flag, and
> removing the dead code.
>
> Signed-off-by: Jeff King <peff@peff.net>
> ---
> We've talked about this off and on for a few years. I don't have any
> immediate plans for any features that need it, but let's get the ball
> rolling.
OK, so this is just callmine canary that can easily be undone when
somebody finds it problematic. Let's give it enough time before we
actually start removing the fallback code that are protected by
"#ifndef HAVE_VARIADIC_MACROS" (they are quite well isolated---only
in the usage and trace, which is pretty much expected as we'd be
using the feature for printf-like macros).
Thanks.
> git-compat-util.h | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/git-compat-util.h b/git-compat-util.h
> index 104993b975..5d5e47fbe2 100644
> --- a/git-compat-util.h
> +++ b/git-compat-util.h
> @@ -1176,9 +1176,12 @@ static inline int regexec_buf(const regex_t *preg, const char *buf, size_t size,
> #endif
> #endif
>
> -#if defined(__GNUC__) || (_MSC_VER >= 1400) || defined(__C99_MACRO_WITH_VA_ARGS)
> +/*
> + * This is always defined as a first step towards making the use of variadic
> + * macros unconditional. If it causes compilation problems on your platform,
> + * please report it to the Git mailing list at git@vger.kernel.org.
> + */
> #define HAVE_VARIADIC_MACROS 1
> -#endif
>
> /* usage.c: only to be used for testing BUG() implementation (see test-tool) */
> extern int BUG_exit_code;
next prev parent reply other threads:[~2021-01-28 6:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 5:28 [PATCH] git-compat-util: always enable variadic macros Jeff King
2021-01-28 6:13 ` Junio C Hamano [this message]
2021-01-29 2:11 ` brian m. carlson
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=xmqq5z3hy4fq.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).