+2002-11-14 Akim Demaille <akim@epita.fr>
+
+ * doc/autoconf.texi (C Compiler): Solitary backslashes.
+ From Paul Eggert and Albert Chin-A-Young.
+
2002-11-14 Kevin Ryde <user42@zip.com.au>
* lib/autoconf/c.m4 (AC_LANG_FUNC_LINK_TRY(C)): Initialize f=$1 rather
@node C Compiler
@subsection C Compiler Characteristics
+The following macros provide ways to find and exercise a C Compiler.
+There are a few constructs that ought to be avoided, but do not deserve
+being checked for, since they can easily be worked around.
+
+@table @asis
+@item Don't use lines containing solitary backslashes
+They tickle a bug in the HP-UX C compiler (checked on HP-UX 10.20,
+11.00, and 11i). Running the compiler on the following source,
+
+@example
+#ifdef __STDC__
+/\
+* A comment with backslash-newlines in it. %@{ %@} *\
+\
+/
+char str[] = "\\
+" A string with backslash-newlines in it %@{ %@} \\
+"";
+char apostrophe = '\\
+\
+'\
+';
+#endif
+@end example
+
+@noindent
+yields
+
+@example
+@error{}cpp: "foo.c", line 13: error 4048: Non-terminating comment at end of file.
+@error{}cpp: "foo.c", line 13: error 4033: Missing #endif at end of file.
+@end example
+
+@noindent
+Removing the lines with solitary backslashes solves the problem.
+@end table
+
@defmac AC_PROG_CC (@ovar{compiler-search-list})
@acindex PROG_CC
@ovindex CC