obsolescent.
* NEWS: Document this.
+2007-04-06 Paul Eggert <eggert@cs.ucla.edu>
+
+ * doc/autoconf.texi (Particular Types): AC_C_LONG_DOUBLE is now
+ obsolescent.
+ * NEWS: Document this.
+
2007-03-29 Paul Eggert <eggert@cs.ucla.edu>
* doc/autoconf.texi (Here-Documents, Limitations of Builtins):
** For portability with the eventual M4 2.0, macros should no longer use
anything larger than $9 to refer to arguments.
+** AC_C_LONG_DOUBLE is obsolescent.
+ The documentation now says that AC_C_LONG_DOUBLE is obsolescent: it
+ tests for problems that are so old that it is no longer of practical
+ importance on current systems. New programs need not use
+ AC_C_LONG_DOUBLE. We have no current plans to remove it.
+
+
* Major changes in Autoconf 2.61a (2006-12-11)
** AC_FUNC_FSEEKO was broken in 2.61; it didn't make fseeko and ftello visible
If the C compiler supports a working @code{long double} type, define
@code{HAVE_LONG_DOUBLE}. The @code{long double} type might have the
same range and precision as @code{double}.
+
+This macro is obsolescent, as current C compilers support @code{long
+double}. New programs need not use this macro.
@end defmac
@defmac AC_TYPE_LONG_DOUBLE_WIDER