Re: AM_INCLUDE is a bad name.

[Alexandre Oliva]

On Feb  6, 2001, Akim Demaille <address@hidden> wrote:

> This is a very bad way.  I don't want to go there, people will ask for
> more and more backward compatibility, and the hell with it.  AU_DEFUN
> and nothing more.

This is a very bad attitude towards our users.  They should be free to
choose whatever versions of autoconf they want their projects to work
with.

Since we already have the machinery to compare autoconf versions,
given AC_PREREQ, why not use it to offer an additional primitive such
as AC_VERSION_CASE(VERSION, CMD, [VERSION, CMD, ...][, CMD])

The pairs VERSION, CMD should have versions in decreasing order.  I
don't see anything wrong it this.  We might even use it ourselves.
Say: we can declare that a certain macro is deprecated, and it will be
removed in version 2.0.  So, we enclose it definition in:

AC_VERSION_CASE(2, [error out or do nothing], [
AU_DEFUN(THE_MACRO, ...)])

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  address@hidden, redhat.com}
CS PhD student at IC-Unicamp        address@hidden, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me