[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AM_INCLUDE is a bad name.
From: |
Akim Demaille |
Subject: |
Re: AM_INCLUDE is a bad name. |
Date: |
05 Feb 2001 17:39:05 +0100 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Crater Lake) |
Pavel Roskin <address@hidden> writes:
> Hello, Tom!
>
> I see that you are not using the latest and greatest Autoconf.
> Names beginning with AM_ are reserved for macros. Autoconf-2.49c will not
> allow such names in configure.
>
> That's why many tests are failing again - AM_INCLUDE is not a good name
> for a variable.
>
> How about renaming AM_INCLUDE to AMINCLUDE everywhere? The patch is
> attached. It fixes all tests.
Tom, you should also know you can have a special exception, and tell
autoconf AM_INCLUDE is OK. But I agree with Pavel it looks way too
much like a macro name, in itself it is confusing.
- AM_INCLUDE is a bad name., Pavel Roskin, 2001/02/05
- Re: AM_INCLUDE is a bad name.,
Akim Demaille <=
- Re: AM_INCLUDE is a bad name., Pavel Roskin, 2001/02/05
- Re: AM_INCLUDE is a bad name., Akim Demaille, 2001/02/06
- Re: AM_INCLUDE is a bad name., Alexandre Oliva, 2001/02/06
- Re: AM_INCLUDE is a bad name., Akim Demaille, 2001/02/07
- Re: AM_INCLUDE is a bad name., Alexandre Oliva, 2001/02/07
- Re: AM_INCLUDE is a bad name., Akim Demaille, 2001/02/07
- Re: AM_INCLUDE is a bad name., Pavel Roskin, 2001/02/07
Re: AM_INCLUDE is a bad name., Tom Tromey, 2001/02/05