===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-5/changes.html,v
retrieving revision 1.75
@@ -123,22 +123,21 @@
<h3 id="c-family">C family</h3>
<ul>
<li>The default setting of the <code>-fdiagnostics-color=</code>
- option is now
- configurable <a href="https://gcc.gnu.org/install/configure.html">when
- building GCC</a> using configuration
- option <code>--with-diagnostics-color=</code>. The possible
- values
+ command-line option is now
+ <a href="https://gcc.gnu.org/install/configure.html">configurable
+ when building GCC</a> using configuration option
+ <code>--with-diagnostics-color=</code>. The possible values
are: <code>never</code>, <code>always</code>, <code>auto</code>
and <code>auto-if-env</code>. The new
- default <code>auto</code> means to use color only when the
+ default <code>auto</code> uses color only when the
standard error is a terminal. The default in GCC 4.9
- was <code>auto-if-env</code>, which defaults to
+ was <code>auto-if-env</code>, which is equivalent to
<code>auto</code> if there is a
non-empty <code>GCC_COLORS</code> environment variable,
and <code>never</code> otherwise. As in GCC 4.9, an empty
<code>GCC_COLORS</code> variable in the environment will
always disable colors, no matter what the default is or what
- command line options are used.</li>
+ command-line options are used.</li>
<li>A new command-line option <code>-Wswitch-bool</code> has been added for
the C and C++ compilers, which warns whenever a <code>switch</code>
statement has an index of boolean type.</li>
On Friday 2014-11-14 19:12, Manuel López-Ibáñez wrote: > This is what I committed. Thanks Manuel! As I am catching up on some older changes, I went ahead and made some minor changes on top of yours and applied the following: Make a link description around -fdiagnostics-color= more meaningful, use "command-line option" consistently, and simplify language. Gerald