public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl dot washington dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/30605] -Wno-tabs should be active for -std=f2003 and -pedantic
Date: Tue, 30 Jan 2007 23:09:00 -0000 [thread overview]
Message-ID: <20070130230920.21500.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30605-11659@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from sgk at troutmask dot apl dot washington dot edu 2007-01-30 23:09 -------
Subject: Re: -Wno-tabs should be active for -std=f2003 and -pedantic
On Tue, Jan 30, 2007 at 11:06:24PM -0000, jb at gcc dot gnu dot org wrote:
>
> ------- Comment #4 from jb at gcc dot gnu dot org 2007-01-30 23:06 -------
> As an aside, aren't -Wtabs and -Wno-tabs reversed? Now -Wno-tabs warns against
> tabs, but shouldn't it be -Wtabs that warns against using them and -Wno-tabs
> should turn the warning off?
>
Well, when I wrote the original patch I interpreted -Wno-tabs
as "No tabs allowed in source", and -Wtabs is its opposite.
We can change this if others want.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30605
next prev parent reply other threads:[~2007-01-30 23:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 22:18 [Bug fortran/30605] New: " jb at gcc dot gnu dot org
2007-01-27 0:02 ` [Bug fortran/30605] " kargl at gcc dot gnu dot org
2007-01-27 0:02 ` kargl at gcc dot gnu dot org
2007-01-27 0:45 ` kargl at gcc dot gnu dot org
2007-01-27 18:01 ` kargl at gcc dot gnu dot org
2007-01-30 23:06 ` jb at gcc dot gnu dot org
2007-01-30 23:09 ` sgk at troutmask dot apl dot washington dot edu [this message]
2007-02-01 11:30 ` jb at gcc dot gnu dot org
2007-02-04 21:32 ` [Bug fortran/30605] [4.2 only] " kargl at gcc dot gnu dot org
2007-02-06 0:28 ` kargl at gcc dot gnu dot org
2007-02-06 0:31 ` kargl at gcc dot gnu dot org
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=20070130230920.21500.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).