This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: proposal to clean up @node Warning Options in invoke.texi
- From: Tom Tromey <tromey at redhat dot com>
- To: gcc at gcc dot gnu dot org
- Date: 10 Jan 2007 06:24:47 -0700
- Subject: Re: proposal to clean up @node Warning Options in invoke.texi
- References: <4543D05A.7080303@mail.mcgill.ca>
- Reply-to: tromey at redhat dot com
>>>>> "Chris" == Chris Pickett <chris.pickett@mail.mcgill.ca> writes:
Chris> For one reason or another, I have spent a fair amount of time
Chris> reading and getting confused by the warnings documentation.
Chris> 3. Get rid of the -Wno-xxx option listings, since it is not always
Chris> the case that -Wxxx is enabled by "default", and this just ends up
Chris> being rather confusing. Instead, explain in the default section that
Chris> everything there can be disabled with -Wno-xxx.
Recently I tried searching the docs for '-Wdeprecated'. There's only
one hit... you have to think to search for '-Wno-deprecated' to find
the actual warning.
So, one cleanup I would like to see is an @opindex for *every* flag.
In particular both -Wfoo and -Wno-foo should both be in the index, so
that a search for either one yields a useful result. (The underlying
idea being that you should be able to copy any option from a command
line into info, and find docs for it.)
Tom