From: Robert Dewar <dewar@gnat.com>
To: base@chatta.us
Cc: Gabriel Dos Reis <gdr@integrable-solutions.net>,
Zack Weinberg <zack@codesourcery.com>,
gcc@gcc.gnu.org
Subject: Re: jFP religious wars
Date: Mon, 22 Mar 2004 13:25:00 -0000 [thread overview]
Message-ID: <405E6BF7.2020808@gnat.com> (raw)
In-Reply-To: <405E6708.70508@chatta.us>
R. D. Flowers wrote:
> But, if some code is broken by -pedantic, isn't it also incorrect in
> SOME picky litte sense?
> That people in some of their actual situations might not care about?
> Similar (in some actual situations) to not caring about that final shred
> of accuracy?
Not at all similar, please review what -pedantic does (don't just
reason from the name :-)
prev parent reply other threads:[~2004-03-22 4:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1079845736.15963.ezmlm@gcc.gnu.org>
2004-03-22 2:08 ` gcc Digest 21 Mar 2004 05:08:56 -0000 Issue 3435 R. D. Flowers
2004-03-22 2:39 ` jFP religious wars R. D. Flowers
2004-03-22 3:35 ` Zack Weinberg
2004-03-22 4:00 ` R. D. Flowers
2004-03-22 8:06 ` Robert Dewar
2004-03-22 8:03 ` Robert Dewar
2004-03-22 11:37 ` Gabriel Dos Reis
2004-03-22 12:45 ` R. D. Flowers
2004-03-22 13:25 ` Robert Dewar [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=405E6BF7.2020808@gnat.com \
--to=dewar@gnat.com \
--cc=base@chatta.us \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=zack@codesourcery.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 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).