[Top][All Lists]

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

Re: CVS Texinfo fails to build the Autoconf manual (from git)

From: Patrice Dumas
Subject: Re: CVS Texinfo fails to build the Autoconf manual (from git)
Date: Tue, 17 Jul 2012 18:43:17 +0200
User-agent: Mutt/1.5.20 (2009-12-10)

On Tue, Jul 17, 2012 at 06:44:31PM +0300, Eli Zaretskii wrote:
> > Date: Tue, 17 Jul 2012 10:19:15 +0200
> > From: Patrice Dumas <address@hidden>
> > Cc: address@hidden, address@hidden, address@hidden
> > 
> > My wild guess is that this strange behaviour of makeinfo in C is a
> > result of the order of expansion that happens by chance, and is not 
> > intended.
> No, it's intended.

You mean that it is intended that the comment is removed as part of the
user defined macro expansion?  makeinfo in C really do remove the end of
line.  The difference with texi2any (unless I missed something) is the
removal of the comment during the macro expansion and not after user
defined macro expansion.

> > In my opinion it is much better to have something consistent, and
> > leaving the end of line out is also better in my opinion, otherwise it
> > is not possible to have a macro expansion within a line.
> If this causes existing uses to break in subtle ways, then I disagree,
> but I've been unable to convince you in the past.

Once again the difference is not on keeping or not the end of line, as I
showed with the examples done with makeinfo in C which do remove the end
of line.  The difference is the order of comment removal with respect to
macro expansion.  This change will break existing uses in subtle ways.
I could try to provide with a backward compatibility mode in which
comments are removed when expanding macros bodies, but I doubt it is
worth it.  It could be interesting to document that change, though.


reply via email to

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