From: kaih@khms.westfalen.de (Kai Henningsen)
To: gcc@gcc.gnu.org
Subject: Re: Lots of suggestions for the gcc manual
Date: Sun, 14 Sep 2003 22:10:00 -0000 [thread overview]
Message-ID: <8trZVHKmw-B@khms.westfalen.de> (raw)
In-Reply-To: <Pine.GSO.4.58.0309130347490.24873@blinky>
stl@caltech.edu (Stephan Thomas Lavavej) wrote on 13.09.03 in <Pine.GSO.4.58.0309130347490.24873@blinky>:
> I propose a clearer layout would be to begin the document with
> -fsyntax-only, -pedantic, -pedantic-errors, and -w as it currently
> does, and then to begin a whole new section: Warnings Included In -Wall.
> Every warning that -Wall enables would go in that section and nothing
> else. If a warning can be further modified, as -Wformat can be, then
> it should link to /another/ section that explains all the modifications
> that can be done, but under no circumstances should any warnings not
> in -Wall appear in the -Wall section.
I have an alternate proposal: every warning that is in -Wall should be
listed as
`-Wformat' (in -Wall)
and similar for -Wextra.
Oh, and for always-on-but-can-be-disabled there should be a similar remark
right after the option name, possibly "(default on)". Similar "(C++ only)"
and whatever else seems appropriate.
Apart from that, I'd like these to be sorted strictly alphabetically.
Another thing that would be very good would be to include the exact
warning text(s) triggered by the warnings; this would make it much easier
to find the relevant option when you have a message (and that option is,
after all, the only place you are likely to find any kind of explanation).
MfG Kai
next prev parent reply other threads:[~2003-09-14 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 15:00 Stephan Thomas Lavavej
2003-09-14 22:10 ` Kai Henningsen [this message]
2003-09-21 17:20 ` Gerald Pfeifer
2003-10-03 18:54 ` PATCH for: " Gerald Pfeifer
2003-10-04 18:38 ` Stephan T. Lavavej
2003-10-05 21:30 ` Gerald Pfeifer
2004-02-16 2:27 ` [PATCH] GCC Warning Options Documentation Stephan T. Lavavej
2004-02-16 3:33 ` James Morrison
2004-03-27 15:38 ` Gerald Pfeifer
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=8trZVHKmw-B@khms.westfalen.de \
--to=kaih@khms.westfalen.de \
--cc=gcc@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).