Re: popdef(undefined), __m4_version__

Hello Eric,

Eric Blake <ebb9 <at> byu.net> writes:
> And this means that m4 1.6 can't 
> be released until after autoconf 2.63 (not that it is too hard to ensure that, 
> as I help maintain both...)

But you don't maintain all Autoconf and M4 packages of all the distros
out there.  For them this is going to be an additional burden to bear.
Esp. as older Autoconf isn't even buildable with m4 1.6.

I fear that this change will just cause m4 1.6 to not be adopted until GCC,
binutils, python, and other packages I'm not aware of have migrated to newer
Autoconf.

Cheers, and sorry for sounding so negative,
Ralf