[Top][All Lists]

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

dumpdef output stream

From: Eric Blake
Subject: dumpdef output stream
Date: Wed, 23 Aug 2006 06:18:54 -0600
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20060719 Thunderbird/ Mnenhy/

Hash: SHA1

In 1.4.x, dumpdef used the trace mechanism for its output, so the -o
option or the debugfile macro could change the dump from stderr to some
other file (or discard it altogether).  In CVS head, revision 1.9 of
modules/m4.c (Aug 2001) changed to unconditionally use stderr
This was post m4-1.4o, but does not show up in NEWS.  Do we want to stick
with this change (meaning I fix my misdocumentation currently in head's
Invoking m4 node, and add a NEWS entry), or stay compatible with the
branch (meaning I revert the change)?  POSIX states that dumpdef goes to
stderr, but a POSIX-compliant usage of m4 will never encounter the -o
option or debugfile macro to change the debug stream to be different than
stderr, so that is not really an issue.

- --
Life is short - so eat dessert first!

Eric Blake             address@hidden
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


reply via email to

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