public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/57869] [C++11] Casting a object pointer to a function pointer should not warn about a forbidden conversion
Date: Tue, 09 Jul 2013 22:19:00 -0000	[thread overview]
Message-ID: <bug-57869-4-mQ4l2vzbMF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57869-4@http.gcc.gnu.org/bugzilla/>

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

Paolo Carlini <paolo.carlini at oracle dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2013-07-09
           Assignee|unassigned at gcc dot gnu.org      |paolo.carlini at oracle dot com
   Target Milestone|---                         |4.9.0
     Ever confirmed|0                           |1

--- Comment #1 from Paolo Carlini <paolo.carlini at oracle dot com> ---
Seems easy to fix. We got this (outdated) comment:

      if (pedantic && (complain & tf_warning))
    /* Only issue a warning, as we have always supported this
       where possible, and it is necessary in some cases.  DR 195
       addresses this issue, but as of 2004/10/26 is still in
       drafting.  */
    warning (0, "ISO C++ forbids casting between pointer-to-function and
pointer-to-object");

thus it seems just matter of suppressing he warning for c++11 (and c++1y) and
updating the comment.


      reply	other threads:[~2013-07-09 22:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09 19:52 [Bug c++/57869] New: " daniel.kruegler at googlemail dot com
2013-07-09 22:19 ` paolo.carlini at oracle dot com [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=bug-57869-4-mQ4l2vzbMF@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).