Re: [PATCH 4/5] Documentation of specific and general cache variables.

[Ralf Wildenhues]

* Paolo Bonzini wrote on Wed, Sep 16, 2009 at 07:28:22AM CEST:
> 
> >>+The result of this macro is cached in the @code{ac_cv_working_alloca_h}
> >>+variable.
> >
> >That doesn't match our conventions, it seems like
> >ac_cv_header_alloca_works might be nicer.  If we document this one, we are
> >stuck with the name.
> 
> I think we already are stuck with the existing names for all cache
> variables, especially because it would be a gratuitous
> incompatibility that autoupdate could not really help with.

We can still introduce new names, and document them, mention they are
new, and their old, obsolete versions, and let the code set *both*
variables.  At least it allows new users to remember only the consistent
rules.

For now, I've not documented ac_cv_working_alloca_h, and added a few
missing 'ac_cv_' prefixes I forgot in the text.

Cheers, and thanks for the reviews,
Ralf