Paul Eggert wrote:
> + * modules/stdnoreturn: Mark as obsolete.
Here too, the classification of a module as "obsolete" is wrong,
because an obsolete module is one which has no effect on any
reasonable portability target.
2022-12-27 Bruno Haible <br...@clisp.org>
stdnoreturn: Mark as deprecated, not obsolete. (Regression 2022-12-24.)
* modules/stdnoreturn (Status): Remove.
(Notice): Say that it is deprecated, not obsolete.
* doc/noreturn.texi: Fix a typo.
diff --git a/doc/noreturn.texi b/doc/noreturn.texi
index ad0a286f4a..748d30ab30 100644
--- a/doc/noreturn.texi
+++ b/doc/noreturn.texi
@@ -25,7 +25,7 @@ data-flow analysis, to declare which functions are
non-returning.
It can also help generate more-efficient code, as there is no need
to save a return address when calling a non-returning function.
-Gnulib has multiple ways to support such a declaration''
+Gnulib has multiple ways to support such a declaration:
@itemize @bullet
@item
diff --git a/modules/stdnoreturn b/modules/stdnoreturn
index ce6b04a35e..e283fd18fb 100644
--- a/modules/stdnoreturn
+++ b/modules/stdnoreturn
@@ -1,11 +1,9 @@
Description:
A <stdnoreturn.h> that nearly conforms to ISO C11.
-Status:
-obsolete
-
Notice:
-This module is obsolete.
+The module 'stdnoreturn' is deprecated.
+New code should use the '_Noreturn' keyword or the 'noreturn' module.
Files:
lib/stdnoreturn.in.h
