Re: AC_FOREACH public?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>>> "KM" == Keith MARSHALL <keith.marshall@xxxxxxxxx> writes:

 KM> When I write my configure.ac, aclocal.m4, or acinclude.m4, *every*
 KM> macro I use is, from my perspective, an *autoconf* macro.  That some
 KM> of these are called AC_*, AS_*, m4_*, or indeed anything else, is
 KM> not important to me -- they are still *autoconf* macros. 

But you are only using the top of the iceberg.  Other people
benefit from this clear layering.

When another user use `autom4te --lang=M4sh' to generate shell
scripts that are not configure scripts, it matters that AS_* and
m4_* are not Autoconf macros, and that m4_forearch is available.

Likewise when you use `autom4te --lang=M4sugar' to process any
kind of input with M4+convenient macros like m4_foreach.
-- 
Alexandre Duret-Lutz



_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf

[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux