Re: config.cache considered harmful

[Jamie Zawinski]

>> I'm not proposing that the config.cache feature be removed, only that
>> it not be made the _default_.
> 
> Sounds reasonable to me.  How about only enabling it when given the
> option --cache-file=<filename>?

For what it's worth, I think that turning the cache file off by default
is the right thing.  Let people who know what they're doing turn it on
explicitly.

On another topic I would guess (but Martin would know better) that a big
part of why xemacs uses its own autoconf is historical: xemacs has been
using autoconf for a very long time, and those early versions of
autoconf really weren't up to the challenge of handling something as
convoluted as emacs...  So at this point there's a lot of historical
baggage in left over from the bad old days.

Does RMSmacs use a modern autoconf, or does it have its own too?

-- 
Jamie Zawinski             [EMAIL PROTECTED]             http://www.jwz.org/