Re: AC_DEFUN_ONCE and maintainability

2012-07-02 Thread Eric Blake
On 07/02/2012 07:22 PM, Bruno Haible wrote: > Hi Paul, > >> How about the name AC_DEF_ONCE instead? > > Yes, this name is equally good, possibly better than AC_ONCE. Technically, the AC_ namespace is reserved for autoconf, and introducing a new AC_ name (whether AC_ONCE or AC_DEF_ONCE) in gnulib

Re: AC_DEFUN_ONCE and maintainability

2012-07-02 Thread Bruno Haible
Hi Paul, > How about the name AC_DEF_ONCE instead? Yes, this name is equally good, possibly better than AC_ONCE. Thanks. Bruno

Re: AC_DEFUN_ONCE and maintainability

2012-07-02 Thread Paul Eggert
On 07/02/2012 06:08 PM, Bruno Haible wrote: > About the naming: The macro FOO in case (C) cannot take arguments and > cannot be invoked; it is far from a "function" - and 'defun' in Lisp > is meant to define a function. Thanks for your careful analysis. I worry that the name AC_ONCE is a bit cryp

AC_DEFUN_ONCE and maintainability

2012-07-02 Thread Bruno Haible
Hi Eric, > The canonical > fix in gnulib is to use AC_DEFUN_ONCE instead of AC_DEFUN for any > function that we want to guarantee that it gets expanded without > triggering the older autoconf bug. You're right; I should revert the patch and use AC_DEFUN_ONCE([gl_FUNC_LOG],...) instead. But I hav