[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: --debugfile behavior
From: |
Eric Blake |
Subject: |
Re: --debugfile behavior |
Date: |
Wed, 24 Dec 2008 18:58:39 +0000 (UTC) |
User-agent: |
Loom/3.14 (http://gmane.org/) |
Eric Blake <ebb9 <at> byu.net> writes:
> > The older spellings
> > of --error-output and -o options do not change in behavior for branch-1.4,
> > although I'm thinking that 2 years has been long enough with --debugfile
> > available that I can make branch-1.6 issue a deprecation warning for those
> > (and thus open the door for m4 2.0 to use -o to specify where output goes,
> > rather than where traces are dumped, consistent with other GNU programs
> > like gcc).
>
> Here's what I'm thinking of applying on branch-1.6:
>
> Subject: [PATCH] Issue deprecation warning for -o/--error-output.
>
> * src/m4.c (main): Add warning for deprecated option.
> * doc/m4.texinfo (Debugging options): Document the change.
> * NEWS: Likewise.
Pushed, after first porting the autoconf 2.61 patch that recognizes --debugfile
back to the autoconf 2.59 branch, in case anyone wants to still build a variant
of autoconf 2.59 that doesn't spit out warnings when used with m4 1.6.
http://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=shortlog;h=branch-2.59
--
Eric Blake