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
This commit is contained in:
Gerald Pfeifer 2011-02-18 00:10:26 +00:00 committed by Gerald Pfeifer
parent d764a8e6bd
commit f73c888214
2 changed files with 9 additions and 3 deletions

View File

@ -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> 2011-02-17 Iain Sandoe <iains@gcc.gnu.org>
* config/darwin-c.c (darwin_cpp_builtins): Define __OBJC2__ for * config/darwin-c.c (darwin_cpp_builtins): Define __OBJC2__ for

View File

@ -4200,9 +4200,10 @@ program will run on. Assertions are usually predefined, but you can
define them with preprocessing directives or command-line options. define them with preprocessing directives or command-line options.
Assertions were intended to provide a more systematic way to describe Assertions were intended to provide a more systematic way to describe
the compiler's target system. However, in practice they are just as the compiler's target system and we added them for compatibility with
unpredictable as the system-specific predefined macros. In addition, they existing compilers. In practice they are just as unpredictable as the
are not part of any standard, and only a few compilers support them. 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 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 of system-specific predefined macros. We recommend you do not use them at
all. all.