From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: Junio C Hamano <gitster@pobox.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
Jeff King <peff@peff.net>
Cc: Jonathan Nieder <jrnieder@gmail.com>, git@vger.kernel.org
Subject: Re: [RFC PATCH] Move SHA-1 implementation selection into a header file
Date: Tue, 14 Mar 2017 23:42:20 +0000 [thread overview]
Message-ID: <1fce97df-7eb8-79d5-b96b-2086746bf19d@ramsayjones.plus.com> (raw)
In-Reply-To: <xmqq1stzio5b.fsf@gitster.mtv.corp.google.com>
On 14/03/17 20:44, Junio C Hamano wrote:
> OK, then I'll queue this. The selection still goes to BASIC_CFLAGS
> so the dependencies for re-compilation should be right, I'd think.
>
> -- >8 --
> From: "brian m. carlson" <sandals@crustytoothpaste.net>
> Date: Sat, 11 Mar 2017 22:28:18 +0000
> Subject: [PATCH] hash.h: move SHA-1 implementation selection into a header file
>
> Many developers use functionality in their editors that allows for quick
> syntax checks, including warning about questionable constructs. This
> functionality allows rapid development with fewer errors. However, such
> functionality generally does not allow the specification of
> project-specific defines or command-line options.
>
> Since the SHA1_HEADER include is not defined in such a case, developers
> see spurious errors when using these tools. Furthermore, while using a
> macro as the argument to #include is permitted by C11, it isn't
> permitted by C89 and C99, and there are known implementations which
> reject it.
C99 certainly allows a macro argument to #include (see, 6.10.2-4; there
is also an example in 6.10.2-8).
I can't remember if it's allowed in C89/C90 (I think it is). I only
have immediate access to the C99 and C11 standards (and I can't be
bothered to search), so I can't say for sure.
ATB,
Ramsay Jones
next prev parent reply other threads:[~2017-03-14 23:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 22:28 [RFC PATCH] Move SHA-1 implementation selection into a header file brian m. carlson
2017-03-12 13:01 ` Jeff King
2017-03-12 16:51 ` brian m. carlson
2017-03-12 20:12 ` Jeff King
2017-03-12 17:54 ` Junio C Hamano
2017-03-14 18:41 ` Jonathan Nieder
2017-03-14 20:14 ` Jeff King
2017-03-14 20:44 ` Junio C Hamano
2017-03-14 21:26 ` Jeff King
2017-03-14 21:50 ` Jonathan Nieder
2017-03-14 23:42 ` Ramsay Jones [this message]
2017-03-14 23:46 ` brian m. carlson
2017-03-15 0:15 ` Ramsay Jones
2017-03-15 15:57 ` Junio C Hamano
2017-03-15 19:48 ` Ramsay Jones
2017-03-14 21:56 ` Jonathan Nieder
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1fce97df-7eb8-79d5-b96b-2086746bf19d@ramsayjones.plus.com \
--to=ramsay@ramsayjones.plus.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).