bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org, Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: [PATCH] stdnoreturn: deprecate
Date: Tue, 27 Dec 2022 11:14:48 +0100	[thread overview]
Message-ID: <3762153.iIbC2pHGDl@nimes> (raw)
In-Reply-To: <20221224093507.207827-1-eggert@cs.ucla.edu>

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  <bruno@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





  reply	other threads:[~2022-12-27 10:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-24  9:35 [PATCH] stdnoreturn: deprecate Paul Eggert
2022-12-27 10:14 ` Bruno Haible [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-27 18:59 [PATCH 0/6] build-aux/bootstrap that doesn't need to replace itself Paul Eggert
2022-12-27 18:59 ` [PATCH] stdnoreturn: deprecate Paul Eggert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3762153.iIbC2pHGDl@nimes \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=eggert@cs.ucla.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).