public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth@dealii.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/11069] C++ Standard Violation (15.3.3)
Date: Mon, 02 Jun 2003 22:23:00 -0000	[thread overview]
Message-ID: <20030602222313.22223.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030602215620.11069.afu@fugmann.dhs.org>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11069


bangerth@dealii.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID
            Summary|C++ Standard Violation      |C++ Standard Violation
                   |(15.3.3)                    |(15.3.3)


------- Additional Comments From bangerth@dealii.org  2003-06-02 22:23 -------
Not a bug. 15.1.3 says:
3 A throw-expression initializes a temporary object, the type  of  which
  is  determined by removing any top-level cv-qualifiers from the static
  type of the operand of throw and adjusting the type from "array of  T"
  or  "function  returning  T" to "pointer to T" or "pointer to function
  returning T", respectively.

Not that it is talking about the _static_ type, not the dynamic type.
Matching of exception handlers is done against this _static_ type.

W.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


      reply	other threads:[~2003-06-02 22:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-02 21:56 [Bug c++/11069] New: " afu@fugmann.dhs.org
2003-06-02 22:23 ` bangerth@dealii.org [this message]

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=20030602222313.22223.qmail@sources.redhat.com \
    --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).