cpp.texi (Obsolete Features): Add background on the origin of assertions.

	* doc/cpp.texi (Obsolete Features): Add background on the
	origin of assertions.

From-SVN: r170261

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 7fecfea528e64819345b4ad7e66de0200b190f39..f44708140de57f33b8540b8aae9c200ceb55b01d 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2011-02-18  Gerald Pfeifer  <gerald@pfeifer.com>
+
+       * doc/cpp.texi (Obsolete Features): Add background on the
+       origin of assertions.
+
 2011-02-17  Iain Sandoe  <iains@gcc.gnu.org>
 
        * config/darwin-c.c (darwin_cpp_builtins): Define __OBJC2__ for

diff --git a/gcc/doc/cpp.texi b/gcc/doc/cpp.texi
index 195fcda39e24c2cb808daddac84fee8f6a2deeae..328cc59fae5e6eba6cbe29bc3c2d2b6204e8c1ab 100644 (file)
--- a/gcc/doc/cpp.texi
+++ b/gcc/doc/cpp.texi
@@ -4200,9 +4200,10 @@ program will run on.  Assertions are usually predefined, but you can
 define them with preprocessing directives or command-line options.
 
 Assertions were intended to provide a more systematic way to describe
-the compiler's target system.  However, in practice they are just as
-unpredictable as the system-specific predefined macros.  In addition, they
-are not part of any standard, and only a few compilers support them.
+the compiler's target system and we added them for compatibility with
+existing compilers.  In practice they are just as unpredictable as the
+system-specific predefined macros.  In addition, they are not part of
+any standard, and only a few compilers support them.
 Therefore, the use of assertions is @strong{less} portable than the use
 of system-specific predefined macros.  We recommend you do not use them at
 all.