[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[SCM] GNU M4 source repository branch, branch-1.6, updated. v1.5.89a-56-
From: |
Eric Blake |
Subject: |
[SCM] GNU M4 source repository branch, branch-1.6, updated. v1.5.89a-56-g27fb700 |
Date: |
Wed, 27 Aug 2008 17:48:30 +0000 |
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 M4 source repository".
http://git.sv.gnu.org/gitweb/?p=m4.git;a=commitdiff;h=27fb700bb7d308ff43691d63eb71b107fc0f5634
The branch, branch-1.6 has been updated
via 27fb700bb7d308ff43691d63eb71b107fc0f5634 (commit)
from d918ca5f34a4653ed4120d5732c8b46738f78bb3 (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 27fb700bb7d308ff43691d63eb71b107fc0f5634
Author: Eric Blake <address@hidden>
Date: Wed Aug 27 11:43:47 2008 -0600
Node renaming in the manual.
* doc/m4.texinfo (Debug Levels): Rename...
(Debugmode): ...to this. All references changed.
(Debug Output): Rename...
(Debugfile): ...to this. All references changed.
(Invoking m4): Fix example, now that order of -d matters.
Signed-off-by: Eric Blake <address@hidden>
-----------------------------------------------------------------------
Summary of changes:
ChangeLog | 9 ++++++++
doc/m4.texinfo | 63 +++++++++++++++++++++++++++----------------------------
2 files changed, 40 insertions(+), 32 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index 1b9bbaa..df022df 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,12 @@
+2008-08-27 Eric Blake <address@hidden>
+
+ Node renaming in the manual.
+ * doc/m4.texinfo (Debug Levels): Rename...
+ (Debugmode): ...to this. All references changed.
+ (Debug Output): Rename...
+ (Debugfile): ...to this. All references changed.
+ (Invoking m4): Fix example, now that order of -d matters.
+
2008-08-23 Eric Blake <address@hidden>
Allow debugmode control over whether defn(undef) warns.
diff --git a/doc/m4.texinfo b/doc/m4.texinfo
index e537c79..8d87cd5 100644
--- a/doc/m4.texinfo
+++ b/doc/m4.texinfo
@@ -201,8 +201,8 @@ How to debug macros and input
* Dumpdef:: Displaying macro definitions
* Trace:: Tracing macro calls
-* Debug Levels:: Controlling debugging output
-* Debug Output:: Saving debugging output
+* Debugmode:: Controlling debugging options
+* Debugfile:: Saving debugging output
Input control
@@ -540,14 +540,13 @@ below as taking effect after any files that occurred
earlier in the
command line. The argument @option{--} is a marker to denote the end of
options.
address@hidden FIXME option -d+f only works on head right now...
With short options, options that do not take arguments may be combined
into a single command line argument with subsequent options, options
with mandatory arguments may be provided either as a single command line
argument or as two arguments, and options with optional arguments must
be provided as a single argument. In other words,
@kbd{m4 -QPDfoo -d a -d+f} is equivalent to
address@hidden -Q -P -D foo -d -d+f -- ./a}, although the latter form is
address@hidden -Q -P -D foo -d ./a -d+f}, although the latter form is
considered canonical.
With long options, options with mandatory arguments may be provided with
@@ -893,7 +892,7 @@ scripts.
@itemx address@hidden@address@hidden|address@hidden@address@hidden
Set the debug-level according to the flags @var{FLAGS}. The debug-level
controls the format and amount of information presented by the debugging
-functions. @xref{Debug Levels}, for more details on the format and
+functions. @xref{Debugmode}, for more details on the format and
meaning of @var{FLAGS}. If omitted, @var{FLAGS} defaults to
@samp{+adeq}. If the option occurs multiple times, @var{FLAGS} starting
with @samp{-} or @samp{+} are cumulative, while @var{FLAGS} starting
@@ -926,8 +925,8 @@ len(`123')
Redirect @code{dumpdef} output, debug messages, and trace output to the
named @var{FILE}. Warnings, error messages, and @code{errprint} output
are still printed to standard error. If unspecified, debug output goes
-to standard error; if empty, debug output is discarded. @xref{Debug
-Output}, for more details. The spellings @option{-o} and
+to standard error; if empty, debug output is discarded.
address@hidden, for more details. The spellings @option{-o} and
@option{--error-output} are misleading and inconsistent with other
@acronym{GNU} tools; for now they are silently accepted as synonyms of
@option{--debugfile}, but in a future version of M4, using them will
@@ -937,7 +936,7 @@ cause a warning to be issued.
@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.
+unlimited. @xref{Debugmode}, for more details.
@item -t @var{NAME}
@itemx address@hidden
@@ -2184,7 +2183,7 @@ A macro definition can be removed with @code{undefine}:
For each argument, remove the macro @var{name}. The macro names must
necessarily be quoted, since they will be expanded otherwise. If an
argument is not a defined macro, then the @samp{d} debug level controls
-whether a warning is issued (@pxref{Debug Levels}).
+whether a warning is issued (@pxref{Debugmode}).
The expansion of @code{undefine} is void.
The macro @code{undefine} is recognized only with parameters.
@@ -2220,7 +2219,7 @@ f(`bye')
@end example
As of M4 1.6, @code{undefine} can warn if @var{name} is not a macro, by
-using @code{debugmode} (@pxref{Debug Levels}) or the command line option
+using @code{debugmode} (@pxref{Debugmode}) or the command line option
@option{-d} (@option{--debugmode}, @pxref{Debugging options, , Invoking
m4}).
@@ -2249,7 +2248,7 @@ the builtin @code{defn}:
Expands to the @emph{quoted definition} of each @var{name}. If an
argument is not a defined macro, the expansion for that argument is
empty, and the @samp{d} debug level controls whether a warning is issued
-(@pxref{Debug Levels}).
+(@pxref{Debugmode}).
If @var{name} is a user-defined macro, the quoted definition is simply
the quoted expansion text. If, instead, @var{name} is a builtin, the
@@ -2416,7 +2415,7 @@ bar
@end example
As of M4 1.6, @code{defn} can warn if @var{name} is not a macro, by
-using @code{debugmode} (@pxref{Debug Levels}) or the command line option
+using @code{debugmode} (@pxref{Debugmode}) or the command line option
@option{-d} (@option{--debugmode}, @pxref{Debugging options, , Invoking
m4}). Also, @code{defn} with multiple arguments can join text with
builtin tokens. However, when defining a macro via @code{define} or
@@ -2492,7 +2491,7 @@ If a macro has several definitions (of which only one is
accessible),
the topmost definition can be removed with @code{popdef}. If there is
no previous definition, @code{popdef} behaves like @code{undefine}, and
if there is no definition at all, the @samp{d} debug level controls
-whether a warning is issued (@pxref{Debug Levels}).
+whether a warning is issued (@pxref{Debugmode}).
The expansion of both @code{pushdef} and @code{popdef} is void.
The macros @code{pushdef} and @code{popdef} are recognized only with
@@ -2566,7 +2565,7 @@ It is possible to temporarily redefine a builtin with
@code{pushdef}
and @code{defn}.
As of M4 1.6, @code{popdef} can warn if @var{name} is not a macro, by
-using @code{debugmode} (@pxref{Debug Levels}) or the command line option
+using @code{debugmode} (@pxref{Debugmode}) or the command line option
@option{-d} (@option{--debugmode}, @pxref{Debugging options, , Invoking
m4}).
@@ -2598,7 +2597,7 @@ Any macro can be called indirectly with @code{indir}:
Results in a call to the macro @var{name}, which is passed the rest of
the arguments @var{args}. If @var{name} is not defined, the expansion
is void, and the @samp{d} debug level controls whether a warning is
-issued (@pxref{Debug Levels}).
+issued (@pxref{Debugmode}).
The macro @code{indir} is recognized only with parameters.
@end deffn
@@ -2692,7 +2691,7 @@ Builtin macros can be called indirectly with
@code{builtin}:
Results in a call to the builtin @var{name}, which is passed the
rest of the arguments @var{args}. If @var{name} does not name a
builtin, the expansion is void, and the @samp{d} debug level controls
-whether a warning is issued (@pxref{Debug Levels}).
+whether a warning is issued (@pxref{Debugmode}).
The macro @code{builtin} is recognized only with parameters.
@end deffn
@@ -3724,8 +3723,8 @@ Fortunately, there is support for macro debugging in
@code{m4}.
@menu
* Dumpdef:: Displaying macro definitions
* Trace:: Tracing macro calls
-* Debug Levels:: Controlling debugging output
-* Debug Output:: Saving debugging output
+* Debugmode:: Controlling debugging options
+* Debugfile:: Saving debugging output
@end menu
@node Dumpdef
@@ -3744,7 +3743,7 @@ it displays the definitions of all known names, otherwise
it displays
the definitions of each @var{name} given. The output is printed to the
current debug file (usually standard error), and is sorted by name. If
a @var{name} is undefined, the @samp{d} debug level controls whether a
-warning is issued (@pxref{Debug Levels}).
+warning is issued (@pxref{Debugmode}).
The expansion of @code{dumpdef} is void.
@end deffn
@@ -3782,7 +3781,7 @@ dumpdef(`f')
@result{}
@end example
address@hidden Levels}, for information on controlling the details of the
address@hidden, for information on controlling the details of the
display.
@node Trace
@@ -3810,8 +3809,8 @@ The expansion of @code{traceon} and @code{traceoff} is
void.
Whenever a traced macro is called and the arguments have been collected,
the call is displayed. If the expansion of the macro call is not void,
the expansion can be displayed after the call. The output is printed
-to the current debug file (defaulting to standard error, @pxref{Debug
-Output}).
+to the current debug file (defaulting to standard error,
address@hidden).
@example
$ @kbd{m4 -d}
@@ -3921,7 +3920,7 @@ m4_eval(m4_divnum)
@result{}0
@end example
address@hidden Levels}, for information on controlling the details of the
address@hidden, for information on controlling the details of the
display. The format of the trace output is not specified by
@acronym{POSIX}, and varies between implementations of @code{m4}.
@@ -3931,7 +3930,7 @@ macro names, and @code{builtin} bypasses macro names
(@pxref{Builtin}),
it is not possible for @code{builtin} to trace which subsidiary builtin
it invokes. If you are worried about tracking all invocations of a
given builtin, you should also trace @code{builtin}, or enable global
-tracing (the @samp{t} debug level, @pxref{Debug Levels}).
+tracing (the @samp{t} debug level, @pxref{Debugmode}).
@example
$ @kbd{m4 -d}
@@ -3989,8 +3988,8 @@ e(`1', `1')
@end example
@end ignore
address@hidden Debug Levels
address@hidden Controlling debugging output
address@hidden Debugmode
address@hidden Controlling debugging options
@cindex controlling debugging output
@cindex debugging output, controlling
@@ -4171,7 +4170,7 @@ include(`foo')dnl
@error{}m4debug: input exhausted
@end example
address@hidden Debug Output
address@hidden Debugfile
@section Saving debugging output
@cindex saving debugging output
@@ -5224,7 +5223,7 @@ it is expected to contain a colon-separated list of
directories, which
will be searched in order.
If the automatic search for include-files causes trouble, the @samp{p}
-debug flag (@pxref{Debug Levels}) can help isolate the problem.
+debug flag (@pxref{Debugmode}) can help isolate the problem.
@node Diversions
@chapter Diverting and undiverting output
@@ -6980,7 +6979,7 @@ Line numbers start at 1 for each file. If the file was
found due to the
@option{-I} option or @env{M4PATH} environment variable, that is
reflected in the file name. The syncline option (@option{-s},
@pxref{Preprocessor features, , Invoking m4}), and the
address@hidden and @samp{l} flags of @code{debugmode} (@pxref{Debug Levels}),
address@hidden and @samp{l} flags of @code{debugmode} (@pxref{Debugmode}),
also use this notion of current file and line. Redefining the three
location macros has no effect on syncline, debug, warning, or error
message output.
@@ -7467,11 +7466,11 @@ line number are accessible through the builtins
@address@hidden,
@item
The format of the output from @code{dumpdef} and macro tracing can be
-controlled with @code{debugmode} (@pxref{Debug Levels}).
+controlled with @code{debugmode} (@pxref{Debugmode}).
@item
The destination of trace and debug output can be controlled with
address@hidden (@pxref{Debug Output}).
address@hidden (@pxref{Debugfile}).
@item
The @code{maketemp} (@pxref{Mkstemp}) macro behaves like @code{mkstemp},
@@ -7616,7 +7615,7 @@ demands on the formatting of that output. Parsing trace
output is not
guaranteed to be reliable, even between different releases of
@acronym{GNU} M4; however, the intent is that any future changes in
trace output will only occur under the direction of additional
address@hidden flags (@pxref{Debug Levels}).
address@hidden flags (@pxref{Debugmode}).
@item
@acronym{POSIX} requires @code{eval} (@pxref{Eval}) to treat all
hooks/post-receive
--
GNU M4 source repository
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [SCM] GNU M4 source repository branch, branch-1.6, updated. v1.5.89a-56-g27fb700,
Eric Blake <=