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 it is addressed to novices, then sticking to AC_DEFUN is safer style. OK - I'll stick to AC_DEFUN ! Cheers, Patrick