public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo dot carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/37811] bind1st fails on mem_fun with reference argument
Date: Mon, 13 Oct 2008 17:14:00 -0000	[thread overview]
Message-ID: <20081013171307.27844.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37811-6594@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from paolo dot carlini at oracle dot com  2008-10-13 17:13 -------
(In reply to comment #6)
> Then I'm hopelessly confused. It's clear that my report and the example in
> DR109 are the same problem. You say: "The example in DR 109 does *not* compile
> if the additional operator() are not added and does when the resolution of DR
> 109 is implemented." That makes sense - with the addition of the overload my
> example will compile too. So it appears that gcc (at least 4.3.1) does *not*
> implement DR109.

No!!!! It does *exactly* implement the DR, it SIMPLY adds the two operator().
Your problem is totally different, has to do with the obnoxious reference to
reference issue, which plagued C++03. The overloads are already there, check
again in the code of the library, but are there to fix a completely different
issue, that reported in DR 109, which has to do with non-const members.

Please, do not re-open PR at your will. This issue is absolutely clear to the
maintainers of the library and nobody (I repeat nobody) will take any further
real action, irrespective of you reopening it or not.


-- 

paolo dot carlini at oracle dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


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


  parent reply	other threads:[~2008-10-13 17:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-12 18:54 [Bug c++/37811] New: " igodard at pacbell dot net
2008-10-13  8:45 ` [Bug libstdc++/37811] " paolo dot carlini at oracle dot com
2008-10-13 15:20 ` igodard at pacbell dot net
2008-10-13 15:28 ` paolo dot carlini at oracle dot com
2008-10-13 16:07 ` igodard at pacbell dot net
2008-10-13 16:24 ` paolo dot carlini at oracle dot com
2008-10-13 17:03 ` igodard at pacbell dot net
2008-10-13 17:14 ` paolo dot carlini at oracle dot com [this message]
2008-10-13 17:56 ` igodard at pacbell dot net
2008-10-13 19:09 ` paolo dot 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=20081013171307.27844.qmail@sourceware.org \
    --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).