[SCM] GNU Autoconf source repository branch, master, updated. v2.65-94-gbba5963

[Ralf Wildenhues]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU Autoconf source repository".

http://git.sv.gnu.org/gitweb/?p=autoconf.git;a=commitdiff;h=bba5963d58eea7424e7e5438651c054e5da8241b

The branch, master has been updated
       via  bba5963d58eea7424e7e5438651c054e5da8241b (commit)
       via  fda8d216db30bfead754861455c1de3c52132760 (commit)
       via  c4cb4ffa1d2e8765d6dc180a43cb263dde446787 (commit)
      from  f08d6f4f9f35c08cf7c0dee2f90b1bb2c0fb809e (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit bba5963d58eea7424e7e5438651c054e5da8241b
Author: Ralf Wildenhues <address@hidden>
Date:   Tue Jun 22 20:05:38 2010 +0200

    Clarify nested double-quotes and backquotes shell issues.
    
    * doc/autoconf.texi (Shellology): New anchor for pdksh.
    (Shell Substitutions): Link to it for escaped double-quotes
    within double-quoted backquotes; add ksh example for unescaped
    inner double-quotes problem.
    
    Signed-off-by: Ralf Wildenhues <address@hidden>

commit fda8d216db30bfead754861455c1de3c52132760
Author: Ralf Wildenhues <address@hidden>
Date:   Tue Jun 22 20:27:31 2010 +0200

    Mention Tru64 5.1 fgrep limitation with emtpy patterns.
    
    * doc/autoconf.texi (Limitations of Usual Tools): Update.
    
    Signed-off-by: Ralf Wildenhues <address@hidden>

commit c4cb4ffa1d2e8765d6dc180a43cb263dde446787
Author: Ralf Wildenhues <address@hidden>
Date:   Tue Jun 22 20:26:33 2010 +0200

    Overhaul the manual, esp. the Autotest chapter.
    
    * doc/autoconf.texi (Installation Directory Variables):
    Replace some uses of @var with @code.
    (Special Shell Variables): Fix misordered paragraph about IFS.
    (Writing Testsuites): Include paragraph following AT_TESTED in
    the macro definition.
    (testsuite Invocation): Failed tests are not rerun.
    (testsuite Scripts, Autotest Logs, testsuite Invocation)
    (Making testsuite Scripts): Minor edits for consistency and
    language.
    
    Signed-off-by: Ralf Wildenhues <address@hidden>

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog         |   22 +++++++++++++
 doc/autoconf.texi |   86 +++++++++++++++++++++++++++++-----------------------
 2 files changed, 70 insertions(+), 38 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 52a7bb1..0fc8dbe 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,25 @@
+2010-06-22  Ralf Wildenhues  <address@hidden>
+
+       Clarify nested double-quotes and backquotes shell issues.
+       * doc/autoconf.texi (Shellology): New anchor for pdksh.
+       (Shell Substitutions): Link to it for escaped double-quotes
+       within double-quoted backquotes; add ksh example for unescaped
+       inner double-quotes problem.
+
+       Mention Tru64 5.1 fgrep limitation with emtpy patterns.
+       * doc/autoconf.texi (Limitations of Usual Tools): Update.
+
+       Overhaul the manual, esp. the Autotest chapter.
+       * doc/autoconf.texi (Installation Directory Variables):
+       Replace some uses of @var with @code.
+       (Special Shell Variables): Fix misordered paragraph about IFS.
+       (Writing Testsuites): Include paragraph following AT_TESTED in
+       the macro definition.
+       (testsuite Invocation): Failed tests are not rerun.
+       (testsuite Scripts, Autotest Logs, testsuite Invocation)
+       (Making testsuite Scripts): Minor edits for consistency and
+       language.
+
 2010-06-18  Bruno Haible  <address@hidden>
 
        Document sed -e limitation.
diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index eba61f4..7e97d96 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -2710,10 +2710,10 @@ The directory for installing documentation files in DVI 
format.
 @defvar exec_prefix
 @ovindex exec_prefix
 The installation prefix for architecture-dependent files.  By default
-it's the same as @var{prefix}.  You should avoid installing anything
-directly to @var{exec_prefix}.  However, the default value for
+it's the same as @code{prefix}.  You should avoid installing anything
+directly to @code{exec_prefix}.  However, the default value for
 directories containing architecture-dependent files should be relative
-to @var{exec_prefix}.
+to @code{exec_prefix}.
 @end defvar
 
 @defvar htmldir
@@ -2770,8 +2770,8 @@ The directory for installing PDF documentation.
 
 @defvar prefix
 @ovindex prefix
-The common installation prefix for all files.  If @var{exec_prefix}
-is defined to a different value, @var{prefix} is used only for
+The common installation prefix for all files.  If @code{exec_prefix}
+is defined to a different value, @code{prefix} is used only for
 architecture-independent files.
 @end defvar
 
@@ -14626,6 +14626,7 @@ the standard shell conform to Posix.
 
 @item Pdksh
 @prindex @samp{pdksh}
address@hidden
 A public-domain clone of the Korn shell called @command{pdksh} is widely
 available: it has most of the @samp{ksh88} features along with a few of
 its own.  It usually sets @code{KSH_VERSION}, except if invoked as
@@ -15139,9 +15140,18 @@ esac
 @noindent
 and in fact it is even @emph{more} portable: in the first case of the
 first attempt, the computation of @code{top_srcdir} is not portable,
-since not all shells properly understand 
@code{"address@hidden"@dots{}"@dots{}`"}.
+since not all shells properly understand 
@code{"address@hidden"@dots{}"@dots{}`"},
+for example Solaris 10 ksh:
+
address@hidden
+$ @kbd{foo="`echo " bar" | sed 's, ,,'`"}
+ksh: : cannot execute
+ksh: bar | sed 's, ,,': cannot execute
address@hidden example
+
address@hidden
 Worse yet, not all shells understand @code{"address@hidden"@dots{}\"@dots{}`"}
-the same way.  There is just no portable way to use double-quoted
+the same way (@pxref{pdksh}).  There is just no portable way to use 
double-quoted
 strings inside double-quoted back-quoted expressions (pfew!).
 
 @table @code
@@ -15804,6 +15814,22 @@ setting.  It is okay to use blocks of shell code that 
temporarily change
 the value of @env{IFS} in order to split on another character, but
 remember to restore it before expanding further macros.
 
+Unsetting @code{IFS} instead of resetting it to the default sequence
+is not suggested, since code that tries to save and restore the
+variable's value will incorrectly reset it to an empty value, thus
+disabling field splitting:
+
address@hidden
+unset IFS
+# default separators used for field splitting
+
+save_IFS=$IFS
+IFS=:
+# ...
+IFS=$save_IFS
+# no field splitting performed
address@hidden example
+
 @item LANG
 @itemx LC_ALL
 @itemx LC_COLLATE
@@ -15827,22 +15853,6 @@ environment variables be set to @samp{C} if the C 
locale is desired;
 @file{configure} scripts and M4sh do that for you.
 Export these variables after setting them.
 
-Unsetting @code{IFS} instead of resetting it to the default sequence
-is not suggested, since code that tries to save and restore the
-variable's value will incorrectly reset it to an empty value, thus
-disabling field splitting:
-
address@hidden
-unset IFS
-# default separators used for field splitting
-
-save_IFS=$IFS
-IFS=:
-# ...
-IFS=$save_IFS
-# no field splitting performed
address@hidden example
-
 @c  However, some older, nonstandard
 @c  systems (notably SCO) break if locale environment variables
 @c  are set to @samp{C}, so when running on these systems
@@ -17809,6 +17819,8 @@ replacement @code{grep -F}.  Also, some traditional 
implementations do
 not work on long input lines.  To work around these problems, invoke
 @code{AC_PROG_FGREP} and then use @code{$FGREP}.
 
+Tru64/OSF 5.1 @command{fgrep} does not match an empty pattern.
+
 
 @item @command{find}
 @c -----------------
@@ -23216,7 +23228,7 @@ interactive tool testing, which is probably its main 
limitation.
 
 Generating testing or validation suites using Autotest is rather easy.
 The whole validation suite is held in a file to be processed through
address@hidden, itself using GNU M4 under the scene, to
address@hidden, itself using GNU M4 under the hood, to
 produce a stand-alone Bourne shell script which then gets distributed.
 Neither @command{autom4te} nor GNU M4 are needed at
 the installer's end.
@@ -23310,7 +23322,7 @@ Files used in configuring a software package:
 @end example
 
 @noindent
-Files created during the test suite execution:
+Files created during test suite execution:
 
 @example
 atconfig -->.                    .--> testsuite.log
@@ -23331,7 +23343,6 @@ need, but therefore most of the time it contains all 
that is needed:
 
 @table @asis
 @item command line arguments
address@hidden akim s/to consist in/to consist of/
 A bad but unfortunately widespread habit consists of
 setting environment variables before the command, such as in
 @samp{CC=my-home-grown-cc ./testsuite}.  The test suite does not
@@ -23357,7 +23368,7 @@ while running programs on a machine @var{host}.  It is 
much simpler to
 run both the test suite and the programs on @var{host}, but then, from
 the point of view of the test suite, there remains a single environment,
 @var{host} = @var{build}.  The log contains relevant information on the
-state of the build machine, including some important environment
+state of the @var{build} machine, including some important environment
 variables.
 @c FIXME: How about having an M4sh macro to say `hey, log the value
 @c of address@hidden'?  This would help both Autoconf and Autotest.
@@ -23496,7 +23507,6 @@ Log the file name and answer to @option{--version} of 
each program in
 space-separated list @var{executables}.  Several invocations register
 new executables, in other words, don't fear registering one program
 several times.
address@hidden defmac
 
 Autotest test suites rely on @env{PATH} to find the tested program.
 This avoids the need to generate absolute names of the various tools, and
@@ -23505,6 +23515,7 @@ programs are being exercised is crucial to 
understanding problems in
 the test suite itself, or its occasional misuses.  It is a good idea to
 also subscribe foreign programs you depend upon, to avoid incompatible
 diagnostics.
address@hidden defmac
 
 @sp 1
 
@@ -23536,7 +23547,7 @@ test group.  This makes it possible to run ``slices'' 
of the test suite.
 For instance, if some of your test groups exercise some @samp{foo}
 feature, then using @samp{AT_KEYWORDS(foo)} lets you run
 @samp{./testsuite -k foo} to run exclusively these test groups.  The
address@hidden of the test group is automatically recorded to
address@hidden of the test group is automatically recorded to
 @code{AT_KEYWORDS}.
 
 Several invocations within a test group accumulate new keywords.  In
@@ -23645,7 +23656,7 @@ If the value of the @var{stdout} or @var{stderr} 
parameter is one of the
 literals in the following table, then the test treats the output
 according to the rules of that literal.  Otherwise, the value of the
 parameter is treated as text that must exactly match the output given by
address@hidden on standard out and standard error (including an empty
address@hidden on standard output and standard error (including an empty
 parameter for no output); any differences are captured in the testsuite
 log and the test is failed (unless an unexpected exit status of 77
 skipped the test instead).  The difference between @code{AT_CHECK} and
@@ -23808,10 +23819,9 @@ keywords.
 
 @sp 1
 
-By default all tests are performed (or described with
address@hidden) in the default environment first silently, then
-verbosely, but the environment, set of tests, and verbosity level can be
-tuned:
+By default all tests are performed (or described with @option{--list})
+silently in the default environment, but the environment, set of tests,
+and verbosity level can be tuned:
 
 @table @samp
 @item @address@hidden
@@ -23868,7 +23878,7 @@ containing @samp{FUNC}.
 
 @item --errexit
 @itemx -e
-If any test fails, immediately abort testing.  It implies
+If any test fails, immediately abort testing.  This implies
 @option{--debug}: post test group clean up, and top-level logging
 are inhibited.  This option is meant for the full test
 suite, it is not really useful for generated debugging scripts.
@@ -23890,11 +23900,11 @@ results are colored if standard output is connected 
to a terminal.
 
 @item --debug
 @itemx -d
-Do not remove the files after a test group was performed ---but they are
+Do not remove the files after a test group was performed---but they are
 still removed @emph{before}, therefore using this option is sane when
 running several test groups.  Create debugging scripts.  Do not
 overwrite the top-level
-log (in order to preserve supposedly existing full log file).  This is
+log (in order to preserve a supposedly existing full log file).  This is
 the default for debugging scripts, but it can also be useful to debug
 the testsuite itself.
 
@@ -24045,7 +24055,7 @@ atlocal: $(srcdir)/atlocal.in 
$(top_builddir)/config.status
 @noindent
 and manage to have @code{$(EXTRA_DIST)} distributed.  You will also want
 to distribute the file @file{build-aux/@/missing} from the Automake
-project; a copy of this file resides in the Autoconf source.
+project; a copy of this file resides in the Autoconf source tree.
 
 With all this in place, and if you have not initialized @samp{TESTSUITEFLAGS}
 within your makefile, you can fine-tune test suite execution with this


hooks/post-receive
-- 
GNU Autoconf source repository