[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AM_INCLUDE is a bad name.
From: |
Tom Tromey |
Subject: |
Re: AM_INCLUDE is a bad name. |
Date: |
06 Feb 2001 12:01:14 -0700 |
>>>>> "Pavel" == Pavel Roskin <address@hidden> writes:
Pavel> After another consideration I decided that AM_INCLUDE is not
Pavel> meant to be private since it appears in AC_SUBST.
But it is meant to be private. It is an implementation detail. If we
change the implementation it might just go away -- leaving user code
using it broken.
There's no way to have a "private" AC_SUBST. That is what namespaces,
even ad hoc ones, are for.
Pavel> I believe that we should move towards "use strict" in
Pavel> automake.in. Although it would catch just few errors, strict
Pavel> typing in large projects (which Automake already is) is usually
Pavel> worth it.
I don't have a problem with this.
Tom
- Re: AM_INCLUDE is a bad name., (continued)
- 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