* Benefits::
* Library vs Reusable Code::
* Portability and Application Code::
+* Target Platforms::
* Modules::
* Various Kinds of Modules::
* Collaborative Development::
The body of the test, then, contains many @code{ASSERT} invocations. When
a test fails, the @code{ASSERT} macro prints the line number of the failing
-statement, thus giving you as a developer a idea which part of the test
+statement, thus giving you, the developer, an idea of which part of the test
failed, even when you don't have access to the machine where the test failed
and the reporting user cannot run a debugger.
* alloca::
* alloca-opt::
* Safe Allocation Macros::
+* Compile-time Assertions::
+* Integer Properties::
* String Functions in C Locale::
* Quoting::
* error and progname::
@include safe-alloc.texi
+@include verify.texi
+
+@include intprops.texi
+
@node String Functions in C Locale
@section Character and String Functions in C Locale