[Top][All Lists]

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

Re: divert()/m4_divert() broken in autoconf-2.64+

From: Ralf Wildenhues
Subject: Re: divert()/m4_divert() broken in autoconf-2.64+
Date: Tue, 24 Nov 2009 14:28:22 +0100
User-agent: Mutt/1.5.20 (2009-08-09)

Hello Mike, Eric,

* Mike Frysinger wrote on Sun, Nov 22, 2009 at 12:31:28AM CET:
> On Saturday 21 November 2009 17:46:19 Eric Blake wrote:
> > According to Mike Frysinger on 11/21/2009 3:47 PM:
> > > the autoconf documentation here is a far cry from anything you can point
> > > at and say "this is a bug in your code".  all it says:
> > >   it is nicer to associate a name with each diversion; the diversion
> > > number associated with a particular diversion name is an implementation
> > > detail, so you should only use diversion names
> > 
> > Documentation patches welcome.
> as i said earlier, i dont really get this diversion stuff, nor do i know the 
> actual limits that are in play here.  you seem to.

The manual already states a bit further down:

     For now, the named diversions of Autoconf and Autoheader, and the
  remaining diversions of Autotest, are not documented.  In other words,
  intentionally outputting text into an undocumented diversion is subject
  to breakage in a future release of Autoconf.

What's more, the example as you originally posted it (and I remember a
very similar real-world example) used diversions "by accident" so to
speak: there was no real need or intentional exploitation of diversion
functionality at all.  It would be a lot easier to argue for a better
API from the Autoconf side if there was some legitimate use case.


reply via email to

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