From: Pavel Roskin <proski@gnu.org>
To: Olivier Galibert <galibert@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Avoid C++ comments, use C comments instead
Date: Tue, 11 Jul 2006 01:17:27 -0400 [thread overview]
Message-ID: <1152595047.29932.9.camel@dv> (raw)
In-Reply-To: <20060710114117.GA62514@dspnet.fr.eu.org>
Hello!
On Mon, 2006-07-10 at 13:41 +0200, Olivier Galibert wrote:
> Supporting old, not-standard-anymore compilers has a cost in
> maintainability, by precluding the use of better constructs (//
> comments, declarations near initialisation, struct initializers...).
> Additionally, it gets harder and harder to have people test for them.
Sorry for one more addition to this thread. I just want to clear some
misunderstanding. The whole point of fixing the comments is to make is
easier to test for other compatibility issues using gcc.
For gcc to report post-c89 features, "-pedantic -std=c89" should be
supplied. This option makes gcc report the c99 comments as errors and
other c99 features as warnings. The errors would stand in the way of
finding the warnings.
I'm not saying all non-c89 constructs should be fixed, but if we get a
report that some feature is not working with some compiler, we could
compile git with "-pedantic -std=c89", find corresponding warnings and
fix them. The comments would stand in the way for somebody using gcc.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2006-07-11 5:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 6:57 [PATCH] Avoid C++ comments, use C comments instead Pavel Roskin
2006-07-10 7:46 ` Junio C Hamano
2006-07-10 9:46 ` Olivier Galibert
2006-07-10 11:06 ` Johannes Schindelin
2006-07-10 11:41 ` Olivier Galibert
2006-07-10 19:14 ` Paul Serice
2006-07-10 20:24 ` Olivier Galibert
2006-07-10 22:55 ` Johannes Schindelin
2006-07-10 23:25 ` Yakov Lerner
2006-07-10 23:51 ` Olivier Galibert
2006-07-11 0:15 ` Shawn Pearce
2006-07-11 0:34 ` Junio C Hamano
2006-07-10 23:42 ` Olivier Galibert
2006-07-11 5:17 ` Pavel Roskin [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:
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=1152595047.29932.9.camel@dv \
--to=proski@gnu.org \
--cc=galibert@pobox.com \
--cc=git@vger.kernel.org \
/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).