public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/12255] exception-specification ignored on pointer to function
Date: Wed, 08 Jun 2011 21:24:00 -0000 [thread overview]
Message-ID: <bug-12255-4-d9V4n1jgcN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-12255-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12255
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at gcc dot gnu.org
Summary|exception-specifications |exception-specification
|unchecked during assignment |ignored on pointer to
|of pointer to function |function
Severity|enhancement |normal
--- Comment #6 from Jason Merrill <jason at gcc dot gnu.org> 2011-06-08 21:22:30 UTC ---
The underlying issue is that G++ just ignores exception-specifications on
non-function declarations. I think this choice originated in the uncertainty
about whether or not the exeception-specification would become part of a
function type rather than remain associated with the declaration. And as it
happens, DR 92 (http://www.open-std.org/JTC1/SC22/WG21/docs/cwg_active.html#92)
is still open...
next parent reply other threads:[~2011-06-08 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12255-4@http.gcc.gnu.org/bugzilla/>
2011-06-08 21:24 ` jason at gcc dot gnu.org [this message]
2021-08-09 19:08 ` [Bug c++/12255] [C++98/11/14 only] " pinskia at gcc dot gnu.org
2021-11-06 4:55 ` pinskia at gcc dot gnu.org
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=bug-12255-4-d9V4n1jgcN@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).