On Sat, 8 Nov 2003 22:09:14 +0000, "Patrick Welche" <prlw1@xxxxxxxxxxxxxx> said: > On Tue, Nov 04, 2003 at 01:58:01PM +0100, Akim Demaille wrote: > > > Why the change AC_DEFUN -> m4_define ? > > > > It is lightweight. I recommend using m4_define for Autoconf authors > > when they can, as it speeds up the process, and in some case, it's > > even better for error messages. Nevertheless, the users should not > > care about this possibility. > > Does that mean that in some package's .m4 files, I should use AC_DEFUN, > but if contributing to lib/autoconf/*.m4 I should use m4_define ? > Or are there specifically things which you aren't allowed to do in > a macro defined using m4_define? If a macro is to AC_REQUIRE another macro, or is itself to be AC_REQUIRED, or if aclocal is to detect a call of the macro in configure.ac and add its definition to aclocal.m4, then use AC_DEFUN. If a macro is a helper macro that is not visible to users, then m4_define can be used. Cheers, Gary. -- ())_. Gary V. Vaughan gary@(lilith.warpmail.net|gnu.org) ( '/ Research Scientist http://www.oranda.demon.co.uk ,_())____ / )= GNU Hacker http://www.gnu.org/software/libtool \' `& `(_~)_ Tech' Author http://sources.redhat.com/autobook =`---d__/