[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gcc -Wall warning for minmax.h
From: |
Derek Price |
Subject: |
Re: gcc -Wall warning for minmax.h |
Date: |
Tue, 07 Jun 2005 10:19:47 -0400 |
User-agent: |
Mozilla Thunderbird 1.0.2 (Windows/20050317) |
Stepan Kasal wrote:
>- We need to document also AS_LITERAL_IF and m4_fatal
> (And you could also document m4_warning, when you are at it.)
>
>
I'll see about it after I get comments on the first round back.
>- we have to document also the fact that AS_TR_SH & AS_TR_CPP expand
> to literal variable (symbol) name, if their argument is a literal
>
>
I didn't think this was important from the user's perspective. I showed
in my examples that variables were expanded properly before conversion,
but I didn't think it important to mention here that expansion of input
without shell meta-characters would be optimized.
Cheers,
Derek
- Re: [bug-gnulib] Re: gcc -Wall warning for minmax.h, (continued)
- Re: [bug-gnulib] Re: gcc -Wall warning for minmax.h, James Youngman, 2005/06/03
- [bug-gnulib] Re: gcc -Wall warning for minmax.h, Bruno Haible, 2005/06/03
- Re: [bug-gnulib] Re: gcc -Wall warning for minmax.h, Derek Price, 2005/06/03
- Re: gcc -Wall warning for minmax.h, Derek Price, 2005/06/06
- Re: gcc -Wall warning for minmax.h, Stepan Kasal, 2005/06/07
- Re: gcc -Wall warning for minmax.h,
Derek Price <=
- Re: gcc -Wall warning for minmax.h, Stepan Kasal, 2005/06/07
- Re: gcc -Wall warning for minmax.h, Derek Price, 2005/06/10
- Re: gcc -Wall warning for minmax.h, Paul Eggert, 2005/06/10
- Re: gcc -Wall warning for minmax.h, Derek Price, 2005/06/10
[bug-gnulib] Re: gcc -Wall warning for minmax.h, Stepan Kasal, 2005/06/04