autoconf-patches
[Top][All Lists]
Advanced

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

Re: [PATCH] Make AC_COMPUTE_INT public


From: Stepan Kasal
Subject: Re: [PATCH] Make AC_COMPUTE_INT public
Date: Wed, 28 Jun 2006 16:52:30 +0200
User-agent: Mutt/1.4.2.1i

Hello,
  I haven't fully reviewed your patch, so just a few trivial
comments:

1) My cleanup of _AC_COMPUTE_INT actually changes only
_AC_COMPUTE_INT_COMPILE, so it is orthogonal to this patch.

2) I think there is a typo in your news entry:

On Wed, Jun 28, 2006 at 03:20:05PM +0200, Paolo Bonzini wrote:
> +** The functionality of the undocumented _AC_COMPUTE_INT is now provided
> +  by a public and documented macro, AC_COMPUTE_INT.  The parameters to the
> +  two functions are different, so autoupdate will change the old private name
> +  to the new one.  _AC_COMPUTE_INT may be removed in a future release.

"autoupdate will not change", right?

3)
> -# _AC_COMPUTE_INT(EXPRESSION, VARIABLE, PROLOGUE, IF-FAILS)
> +# _AC_COMPUTE_INT(EXPRESSION, VARIABLE, PROLOGUE, [IF-FAILS])
>  # ---------------------------------------------------------
> -m4_define([_AC_COMPUTE_INT],
> +m4_defun([_AC_COMPUTE_INT],
>  [AC_LANG_COMPILER_REQUIRE()dnl
>  if test "$cross_compiling" = yes; then
...
> +# AC_COMPUTE_INT(MESSAGE, CACHE-ID, EXPRESSION, [PROLOGUE = 
> DEFAULT-INCLUDES],
> +#             [IF-FAILS])
> +# ---------------------------------------------------------
> +m4_defun([AC_COMPUTE_INT],
> +[AC_CACHE_CHECK([$1], [$2],
> +[if test "$cross_compiling" = yes; then

The new version does not contain AC_LANG_COMPILER_REQUIRE()--is that
intentional?  If yes, could you please explain?

Thanks for your work,
        Stepan Kasal




reply via email to

[Prev in Thread] Current Thread [Next in Thread]