Re: config.cache considered harmful

[Akim Demaille]

>>>>> "Martin" == Martin Buchholz <[EMAIL PROTECTED]> writes:

Martin> I think I used `unset'.  And XEmacs' configure uses `unset'
Martin> today, and no one I know of has hit this non-portability.

I claim that machines without Bourne shells supporting unset and
functions are no longer to be considered.  No single guy could name me
such a broken machine.  I'd really love that we move to functions some
day.

How about leaving an implicit test in Autoconf 2.15's configure, with
a message such as `Please warn us that your machine does not support
blah blah.  This message is not a failure notice, the configuration
went smooth, but your machine demonstrates there are things not to
change in Autoconf'.

Or whatever, you get the idea.

        Akim