From: David MacKenzie <djm@djmnet.org>
Date: Wed, 19 Oct 1994 05:42:59 +0000 (+0000)
Subject: minor corrections
X-Git-Tag: fsf-origin~382
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=4118dbc95cbb4e3c54b2651fab21e59785296fff;p=thirdparty%2Fautoconf.git

minor corrections
---

diff --git a/autoconf.texi b/autoconf.texi
index a817433d5..2f4aef7ea 100644
--- a/autoconf.texi
+++ b/autoconf.texi
@@ -574,9 +574,9 @@ autoscan}).
 @code{ifnames} scans all of the C source files named on the command line
 (or the standard input, if none are given) and writes to the standard
 output a sorted list of all the identifiers that appear in those files
-in @code{#if}, @code{#elif}, or @code{#ifdef} directives.  It prints
-each identifier on a line, followed by a space-separated list of the
-files in which that identifier occurs.
+in @code{#if}, @code{#elif}, @code{#ifdef}, or @code{#ifndef}
+directives.  It prints each identifier on a line, followed by a
+space-separated list of the files in which that identifier occurs.
 
 @noindent
 @code{ifnames} accepts the following options:
@@ -4647,8 +4647,8 @@ I looked briefly into using the Metaconfig package, by Larry Wall,
 Harlan Stenn, and Raphael Manfredi, but I decided not to for several
 reasons.  The @code{Configure} scripts it produces are interactive,
 which I find quite inconvenient; I didn't like the ways it checked for
-some features (such as library functions); I didn't know whether it was
-being maintained at that time, and the @code{Configure} scripts I had
+some features (such as library functions); I didn't know that it was
+still being maintained, and the @code{Configure} scripts I had
 seen didn't work on many modern systems (such as System V R4 and NeXT);
 it wasn't very flexible in what it could do in response to a feature's
 presence or absence; I found it confusing to learn; and it was too big
diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index a817433d5..2f4aef7ea 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -574,9 +574,9 @@ autoscan}).
 @code{ifnames} scans all of the C source files named on the command line
 (or the standard input, if none are given) and writes to the standard
 output a sorted list of all the identifiers that appear in those files
-in @code{#if}, @code{#elif}, or @code{#ifdef} directives.  It prints
-each identifier on a line, followed by a space-separated list of the
-files in which that identifier occurs.
+in @code{#if}, @code{#elif}, @code{#ifdef}, or @code{#ifndef}
+directives.  It prints each identifier on a line, followed by a
+space-separated list of the files in which that identifier occurs.
 
 @noindent
 @code{ifnames} accepts the following options:
@@ -4647,8 +4647,8 @@ I looked briefly into using the Metaconfig package, by Larry Wall,
 Harlan Stenn, and Raphael Manfredi, but I decided not to for several
 reasons.  The @code{Configure} scripts it produces are interactive,
 which I find quite inconvenient; I didn't like the ways it checked for
-some features (such as library functions); I didn't know whether it was
-being maintained at that time, and the @code{Configure} scripts I had
+some features (such as library functions); I didn't know that it was
+still being maintained, and the @code{Configure} scripts I had
 seen didn't work on many modern systems (such as System V R4 and NeXT);
 it wasn't very flexible in what it could do in response to a feature's
 presence or absence; I found it confusing to learn; and it was too big