Re: spurious "(cached)" output from AC_CACHE_VAL

[Ralf Wildenhues]

Hello Eric, Bruno,

* Eric Blake wrote on Sat, Feb 28, 2009 at 02:45:06PM CET:
> According to Bruno Haible on 2/27/2009 3:36 PM:
> > 
> > Eric Blake wrote in 
> > <http://lists.gnu.org/archive/html/bug-gnulib/2009-02/msg00213.html>:
> >> But your patch has merit in that it makes a nice macro name that explains 
> >> what 
> >> you are intending.
> > 
> > It would even be better if this macro was not needed. Couldn't AC_CACHE_VAL 
> > be
> > changed to output "(cached)" when run between AC_MSG_CHECKING and
> > AC_MSG_RESULT, and be silent otherwise?
> 
> Wow, nice suggestion for improving the API.  I'll work on that.

I like this, too, but I fear a bit that there may be old configure.in
scripts that don't use the AC_MSG_* pair of macros.  OTOH, a missing
"(cached)" in really odd circumstances isn't all that big a problem.

Otherwise, I like the idea of not publishing the cache feature, thanks.

Cheers,
Ralf