On 2/12/19 9:34 AM, Eric S. Raymond wrote:
If you're willing to assume that your target platforms are compliant with C99 and POSIX-1.2001 this is actually very low-risk.
I agree, and would be happy if Bison assumed that. However, Bison's configure script ports among implementation variants that postdate C99 and POSIX-2001. For example, './configure --enable-gcc-warnings' deduces which GCC warning options your compiler supports, and this set of options differs between GCC 8 and GCC 9, or between GCC and Clang. How would the autoconf cleanup address these post-2001 issues?
