[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AM_INCLUDE is a bad name.
From: |
Alexandre Oliva |
Subject: |
Re: AM_INCLUDE is a bad name. |
Date: |
07 Feb 2001 01:19:10 -0200 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) |
On Feb 5, 2001, Tom Tromey <address@hidden> wrote:
> I'd like to also work out a naming scheme for internally generated
> targets. That way eventually it will be clear what people can rely on
> and what they cannot. Suggestions here are welcome.
How 'bout `_am-target-name'? (note the leading underscore)
--
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
- Re: AM_INCLUDE is a bad name., (continued)
- 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