[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: document m4_foreach*/AC_FOREACH
From: |
Stepan Kasal |
Subject: |
Re: document m4_foreach*/AC_FOREACH |
Date: |
Mon, 20 Feb 2006 15:15:33 +0100 |
User-agent: |
Mutt/1.4.1i |
Hello,
On Sun, Feb 19, 2006 at 05:16:55PM +0100, Ralf Wildenhues wrote:
> > Yes, AC_FOREACH is relatively widely used, but if it managed to escape
> > documentation for so long, we should accept its victory now. ;-)
>
> Did you mean "we should not accept its victory now"?
AC_FOREACH wants to hide. It strived against the documentation all the time.
We should just admit that it has achived that goal.
That's what I meant.
> Look, the chapter says:
> | You may completely skip this chapter if you are new to Autoconf. Its
> | intention is mainly to help maintainers updating their packages by
> | understanding how to move to more modern constructs.
>
> The fact that it is widely used is IMVHO a reason to mention it here,
> not against it: users should learn how to replace it correctly. It
> helps users to be certain that they can safely replace AC_FOREACH with
> m4_foreach_w.
Yes, you are right, it's better if it is documented. Sorry for the fuss.
Thank you very much for the patch!
Stepan
- document m4_foreach*/AC_FOREACH, Ralf Wildenhues, 2006/02/14
- Re: document m4_foreach*/AC_FOREACH, Paul Eggert, 2006/02/15
- Re: document m4_foreach*/AC_FOREACH, Ralf Wildenhues, 2006/02/15
- Re: document m4_foreach*/AC_FOREACH, Eric Blake, 2006/02/16
- Re: document m4_foreach*/AC_FOREACH, Ralf Wildenhues, 2006/02/16
- Re: document m4_foreach*/AC_FOREACH, Eric Blake, 2006/02/16
- Re: document m4_foreach*/AC_FOREACH, Ralf Wildenhues, 2006/02/17
- Re: document m4_foreach*/AC_FOREACH, Stepan Kasal, 2006/02/19
- Re: document m4_foreach*/AC_FOREACH, Ralf Wildenhues, 2006/02/19
- Re: document m4_foreach*/AC_FOREACH,
Stepan Kasal <=
- Re: document m4_foreach*/AC_FOREACH, Ralf Wildenhues, 2006/02/20