public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51379] reinterpret_cast is not particularly useful
Date: Thu, 01 Dec 2011 13:59:00 -0000	[thread overview]
Message-ID: <bug-51379-4-zYoiZNqpME@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51379-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org,
                   |                            |jason at gcc dot gnu.org

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-12-01 13:58:29 UTC ---
I wonder about the C++11 wording though, in C++03 it said:
"The reinterpret_cast operator shall not cast away constness. [Note: see 5.2.11
for the definition of ‘‘casting away constness’’. Subject to the restrictions
in this section, an expression may be cast to its own type using a
reinterpret_cast operator. ]"
but in C++11:
"The reinterpret_cast operator shall not cast away constness (5.2.11). An
expression of integral, enumeration, pointer, or pointer-to-member type can be
explicitly converted to its own type; such a cast yields the
value of its operand."
For the latter wording it isn't obvious if the second sentence is subject to
the other restrictions or not.


  parent reply	other threads:[~2011-12-01 13:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-01 12:57 [Bug c++/51379] New: " piotr.wyderski at gmail dot com
2011-12-01 12:58 ` [Bug c++/51379] " piotr.wyderski at gmail dot com
2011-12-01 13:20 ` redi at gcc dot gnu.org
2011-12-01 13:59 ` jakub at gcc dot gnu.org [this message]
2011-12-01 14:07 ` redi at gcc dot gnu.org
2011-12-31 21:54 ` [Bug c++/51379] [C++0x] [DR 799] " paolo.carlini at oracle dot com
2012-01-01 20:22 ` paolo at gcc dot gnu.org
2012-01-01 20:24 ` paolo.carlini at oracle dot com

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-51379-4-zYoiZNqpME@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).