Index: autoconf.texi
===================================================================
RCS file: /cvs/autoconf/doc/autoconf.texi,v
retrieving revision 1.442
diff -u -r1.442 autoconf.texi
--- autoconf.texi	2001/04/11 14:20:13	1.442
+++ autoconf.texi	2001/04/11 14:41:33
@@ -4466,9 +4466,9 @@
 @cvindex F77_FUNC
 @cvindex F77_FUNC_
 Defines C macros @code{F77_FUNC(name,NAME)} and
address@hidden(name,NAME)} to properly mangle the names of C
-identifiers, and C identifiers with underscores, respectively, so that
-they match the name mangling scheme used by the Fortran 77 compiler.
address@hidden(name,NAME)} to properly mangle the names of C/C++
+identifiers, and identifiers with underscores, respectively, so that
+they match the name-mangling scheme used by the Fortran 77 compiler.
 
 Fortran 77 is case-insensitive, and in order to achieve this the Fortran
 77 compiler converts all identifiers into a canonical case and format.
@@ -4487,12 +4487,10 @@
       end
 @end example
 
-You would then declare its prototype in C as:
+You would then declare its prototype in C or C++ as:
 
 @example
-#ifdef F77_FUNC
-# define FOOBAR_F77 F77_FUNC(foobar,FOOBAR)
-#endif
+#define FOOBAR_F77 F77_FUNC(foobar,FOOBAR)
 #ifdef __cplusplus
 extern "C"  /* prevent C++ name mangling */
 #endif
@@ -4507,9 +4505,10 @@
 
 Although Autoconf tries to be intelligent about detecting the
 name-mangling scheme of the Fortran 77 compiler, there may be Fortran 77
-compilers that it doesn't support yet.  It is therefore recommended that
-you test whether the @code{F77_FUNC} and @code{F77_FUNC_} macros are
-defined, as we have done in the example above.
+compilers that it doesn't support yet.  In this case, the above code
+will generate a compile-time error, but some other behavior
+(e.g. disabling Fortran-related features) can be induced by checking
+whether the @code{F77_FUNC} macro is defined.
 
 Now, to call that routine from a C program, we would do something like: