m4-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Changes to m4/doc/m4.texinfo,v


From: Eric Blake
Subject: Changes to m4/doc/m4.texinfo,v
Date: Wed, 20 Sep 2006 04:04:31 +0000

CVSROOT:        /sources/m4
Module name:    m4
Changes by:     Eric Blake <ericb>      06/09/20 04:04:29

Index: doc/m4.texinfo
===================================================================
RCS file: /sources/m4/m4/doc/m4.texinfo,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -b -r1.47 -r1.48
--- doc/m4.texinfo      19 Sep 2006 13:16:08 -0000      1.47
+++ doc/m4.texinfo      20 Sep 2006 04:04:29 -0000      1.48
@@ -649,22 +649,25 @@
 @var{FLAGS} starts with @samp{-} or @samp{+}, they are cumulative,
 otherwise the later flags override all earlier occurrences.
 
address@hidden address@hidden
address@hidden -o @var{FILE}
address@hidden address@hidden
+Redirect debug and trace output to the named @var{FILE}.  Warnings,
+error messages, and the output of @code{errprint} and @code{dumpdef},
+are still printed to standard error.  If this option is not given, debug
+output goes to standard error; if @var{FILE} is the empty string, debug
+output is discarded.  @xref{Debug Output}, for more details.  The
+spellings @option{-o} and @option{--error-output} are misleading and
+inconsistent with other @acronym{GNU} tools; using those spellings will
+evoke a warning, and they may be withdrawn or change semantics in a
+future release.
+
 @item -l @var{NUM}
 @itemx address@hidden
 Restrict the size of the output generated by macro tracing to @var{NUM}
 characters per trace line.  If unspecified or zero, output is
 unlimited.  @xref{Debug Levels}, for more details.
 
address@hidden -o @var{FILE}
address@hidden address@hidden
address@hidden address@hidden
-Redirect debug and trace output to the named @var{FILE}.  Warnings,
-error messages, and the output of @code{errprint} and @code{dumpdef},
-are still printed to standard error.  @xref{Debug Output}, for more
-details.  The name @option{--error-output} is misleading; using it
-instead of the other spellings will evoke a warning, and it may be
-withdrawn in a future release.
-
 @item -t @var{NAME}
 @itemx address@hidden
 This enables tracing for the macro @var{NAME}, at any point where it is
@@ -1813,6 +1816,7 @@
 @comment FIXME - we don't yet handle mixing text and builtins.  This
 @comment example passes under Solaris (minus the warning).
 
address@hidden xfail
 @example
 defn(`foo')
 @error{}m4:stdin:1: Warning: defn: undefined macro `foo'
@@ -1988,6 +1992,22 @@
 @result{}
 @end example
 
+When a symbol has multiple definitions, thanks to @code{pushdef}, the
+entire stack is renamed.
+
address@hidden
+pushdef(`foo', `1')pushdef(`foo', `2')
address@hidden
+renamesyms(`^foo$', `bar')
address@hidden
+bar
address@hidden
+popdef(`bar')bar
address@hidden
+popdef(`bar')bar
address@hidden
address@hidden example
+
 @node Indir
 @section Indirect call of macros
 
@@ -2554,7 +2574,7 @@
 it displays the definitions of all known names, otherwise it displays
 the definitions of the @var{names} given.  The output is printed
 directly to standard error, independently of the @option{--debugfile}
-option (or @option{-o}, @pxref{Invoking m4}), or @code{debugfile} macro.
+option (@pxref{Invoking m4}), or @code{debugfile} macro.
 The output is sorted by name.  If an unknown name is encountered, a
 warning is printed.
 
@@ -2917,8 +2937,8 @@
 @cindex output, saving debugging
 @cindex @acronym{GNU} extensions
 Debug and tracing output can be redirected to files using either the
address@hidden option to @code{m4} (or @option{-o},
address@hidden m4}), or with the builtin macro @code{debugfile}:
address@hidden option to @code{m4} (@pxref{Invoking m4}), or with
+the builtin macro @code{debugfile}:
 
 @deffn {Builtin (gnu)} debugfile (@ovar{file})
 Send all further debug and trace output to @var{file}, opened in append
@@ -2957,13 +2977,13 @@
 @end example
 
 Although the @option{--safer} option cripples @code{debugfile} to a
-limited subset of capabilities, you may still use the @option{-o}
+limited subset of capabilities, you may still use the @option{--debugfile}
 option from the command line with no restrictions.
 
address@hidden options: --safer -otrace -tfoo -Dfoo=bar -d+l
address@hidden options: --safer --debugfile=trace -tfoo -Dfoo=bar -d+l
 @comment status: 1
 @example
-$ @kbd{m4 --safer -o trace -t foo -D foo=bar -daelq}
+$ @kbd{m4 --safer --debugfile trace -t foo -D foo=bar -daelq}
 foo # traced to `trace'
 @result{}bar # traced to `trace'
 debugfile(`file')
@@ -4876,8 +4896,7 @@
 @deffn {Builtin (m4)} errprint (@var{message}, @dots{})
 You can print error messages using @code{errprint}, which simply prints
 @var{message} and the rest of the arguments on standard error,
-independently of the @option{--debugfile} option (or @option{-o},
address@hidden m4}).
+independently of the @option{--debugfile} option (@pxref{Invoking m4}).
 
 The expansion of @code{errprint} is void.
 @end deffn
@@ -5253,10 +5272,9 @@
 @code{debugfile} (@pxref{Debug Output}).
 @end itemize
 
-In addition to the above extensions, GNU @code{m4} implements the
-following command line options: @samp{-F}, @samp{-G}, @samp{-I},
address@hidden, @samp{-R}, @samp{-V}, @samp{-W}, @samp{-d},
address@hidden, @samp{-o}, @samp{-r} and @samp{-t}.  @xref{Invoking m4},
+Additionally, @acronym{POSIX} only requires support for the command line
+options @samp{-s}, @samp{-D}, and @samp{-U}, so all other options
+accepted by @acronym{GNU} M4 are extensions.  @xref{Invoking m4},
 for a description of these options.
 
 Also, the debugging and tracing facilities in GNU @code{m4} are much




reply via email to

[Prev in Thread] Current Thread [Next in Thread]