list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: "Martin Ågren" <>
To: Jeff King <>
Cc: Git Mailing List <>, Taylor Blau <>
Subject: Re: [PATCH] list-objects-filter-options: fix function name in BUG
Date: Wed, 18 Nov 2020 07:22:08 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, 17 Nov 2020 at 23:54, Jeff King <> wrote:
> I actually wonder if it is time to drop HAVE_VARIADIC_MACROS completely.
> They are in C99, and we have been introducing many other C99-isms. It
> would be a minor cleanup to a few bits of code, which perhaps isn't
> worth the risk. But I also have a vague memory of not being able to
> implement some interfaces because we couldn't count on them.
> Poking around, 3689539127 (add helpers for allocating flex-array
> structs, 2016-02-22) points out one such case. I think discussion of
> BUG_ON() got blocked by that, too. Looks like we also discussed them in
> the big "C99 weather balloon" thread:

Ok, that all makes sense.

> Maybe it's time for something like this as a test:

I had a vague memory that for some weather balloons, we would add a
comment like "please let us know if you trip on this; for your own sake,
don't just patch it locally." But maybe that was just for, e.g.,
01d3a526ad ("t0000: check whether the shell supports the "local"
keyword", 2017-10-26), where we add a test, and a single failing test
might otherwise be easy to ignore.

Which is different to what would happen if every file including
git-compat-util.h and/or each invocation of BUG() would make the
compiler complain.

All in all, this diff makes sense.


      parent reply	other threads:[~2020-11-18  6:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-14  8:43 Martin Ågren
2020-11-17  2:13 ` Jeff King
2020-11-17 18:02   ` Martin Ågren
2020-11-17 22:54     ` Jeff King
2020-11-17 23:07       ` Eric Sunshine
2020-11-18  2:08         ` Jeff King
2020-11-18  2:24       ` Jonathan Nieder
2020-11-18  6:22       ` Martin Ågren [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:

  List information:

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

  git send-email \
    --in-reply-to='' \ \ \ \ \
    --subject='Re: [PATCH] list-objects-filter-options: fix function name in BUG' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

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).