All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Elia Pinto <gitter.spiros@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 00/22] add the FORMATPRINTF macro to declare the gcc function
Date: Thu, 11 Feb 2016 09:59:21 -0800	[thread overview]
Message-ID: <xmqq37szxh52.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1455194339-859-1-git-send-email-gitter.spiros@gmail.com> (Elia Pinto's message of "Thu, 11 Feb 2016 12:38:37 +0000")

Elia Pinto <gitter.spiros@gmail.com> writes:

> Add the FORMATPRINTF macro for declaring the gcc function attribute 'format printf'
> for code style consistency with similar macro that git already use for other gcc
> attributes. And use it where necessary.
>
> Elia Pinto (22):
>   git-compat-util.h: add the FORMATPRINTF macro

Hmm.  Given that we already have

#ifndef __GNUC__
#ifndef __attribute__
#define __attribute__(x)
#endif
#endif

in git-compat-util.h, it is really between:

    __attribute__((format (printf, 1, 2)))
    void advise(const char *advice, ...);

    __attribute__((format (printf,2,3)))
    extern void strbuf_addf(struct strbuf *sb, const char *fmt, ...);

and

    FORMATPRINTF(1,2)
    void advise(const char *advice, ...);

    FORMATPRINTF(2,3)
    extern void strbuf_addf(struct strbuf *sb, const char *fmt, ...);


Perhaps I am biased for staring at our source code for too long, but
somehow the latter looks unnecessarily loud, spelled in all caps.

I dunno.  What does this really buy us?

  parent reply	other threads:[~2016-02-11 17:59 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11 12:38 [PATCH 00/22] add the FORMATPRINTF macro to declare the gcc function Elia Pinto
2016-02-11 12:38 ` [PATCH 01/22] git-compat-util.h: add the FORMATPRINTF macro Elia Pinto
2016-02-11 12:38 ` [PATCH 02/22] advice.h: use the FORMATPRINTF macro to declare the gcc function attribute 'format printf' Elia Pinto
2016-02-11 12:38 ` [PATCH 03/22] argv-array.h: " Elia Pinto
2016-02-11 20:53   ` Junio C Hamano
2016-02-11 21:49     ` Junio C Hamano
2016-02-11 12:38 ` [PATCH 04/22] builtin/index-pack.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 05/22] builtin/receive-pack.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 06/22] builtin/update-index.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 07/22] builtin/upload-archive.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 08/22] cache.h: " Elia Pinto
2016-02-11 12:38 ` [PATCH 09/22] color.h: " Elia Pinto
2016-02-11 12:38 ` [PATCH 10/22] config.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 11/22] daemon.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 12/22] fsck.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 13/22] http-backend.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 14/22] imap-send.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 15/22] merge-recursive.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 16/22] pkt-line.h: " Elia Pinto
2016-02-11 12:38 ` [PATCH 17/22] remote.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 18/22] strbuf.h: " Elia Pinto
2016-02-11 12:38 ` [PATCH 19/22] trace.h: " Elia Pinto
2016-02-11 12:38 ` [PATCH 20/22] transport-helper.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 21/22] utf8.h: " Elia Pinto
2016-02-11 12:38 ` [PATCH 22/22] wt-status.h: " Elia Pinto
2016-02-11 17:59 ` Junio C Hamano [this message]
2016-02-11 22:33   ` [PATCH 00/22] add the FORMATPRINTF macro to declare the gcc function Jeff King
2016-02-18 21:59     ` Junio C Hamano

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=xmqq37szxh52.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitter.spiros@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.