public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
	 DJ Delorie <dj@redhat.com>,
	 libc-alpha@sourceware.org
Subject: Re: __THROW → __NOEXCEPT
Date: Tue, 04 Jun 2024 18:34:59 +0200	[thread overview]
Message-ID: <87bk4gsm30.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <587b8176-62e4-435f-8125-3adb29e32653@cs.ucla.edu> (Paul Eggert's message of "Tue, 4 Jun 2024 09:21:19 -0700")

* Paul Eggert:

> On 2024-06-04 05:39, Florian Weimer wrote:
>> * Adhemerval Zanella Netto:
>> 
>>>> (Who decided __THROW means "doesn't throw" ?)
>>> That is an excellent question...
>> It stands for throw(), the old version of the C++ noexcept specifier
>> which could also contain an explicit exception list.
>
> Would anyone object to renaming __THROW to __NOEXCEPT? C++11 renamed
> 'throw' to 'noexcept' and C++20 removed 'throw', so using __NOEXCEPT
> would make headers more readable to today's users.

I'm not sure if it's worth the update churn, but please make it
__NOEXCEPT_LEAF and use __NOEXCEPT for for __THROWNL.

And we really can't remove the old macros, they are widely used.

Thanks,
Florian


  reply	other threads:[~2024-06-04 16:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 17:26 [PATCH 0/2] difftime isn't even pure Paul Eggert
2024-05-28 17:26 ` [PATCH 1/2] difftime can throw exceptions Paul Eggert
2024-06-03 22:01   ` DJ Delorie
2024-06-04 11:36     ` Adhemerval Zanella Netto
2024-06-04 12:39       ` Florian Weimer
2024-06-04 16:21         ` __THROW → __NOEXCEPT (was: difftime can throw exceptions) Paul Eggert
2024-06-04 16:34           ` Florian Weimer [this message]
2024-06-04 16:42   ` [PATCH 1/2] difftime can throw exceptions Florian Weimer
2024-06-04 19:33     ` Paul Eggert
2024-06-04 20:52       ` Florian Weimer
2024-06-04 22:53         ` Paul Eggert
2024-05-28 17:26 ` [PATCH 2/2] Improve doc for time_t range (BZ 31808) Paul Eggert
2024-06-03 23:39   ` DJ Delorie

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

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

  git send-email \
    --in-reply-to=87bk4gsm30.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=dj@redhat.com \
    --cc=eggert@cs.ucla.edu \
    --cc=libc-alpha@sourceware.org \
    /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).