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 16:24:00 -0000	[thread overview]
Message-ID: <20081013162308.6861.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37811-6594@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from paolo dot carlini at oracle dot com  2008-10-13 16:23 -------
(In reply to comment #4)
> Ah - I was looking at language DR109, not library DR109. However, the correct
> DR says the committee approved the example reported here (and adds the fix) so
> gcc appears to be in error to fail it.

That't *not* true. 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.

 However, there is the curious remark:
>     "Howard believes there is a flaw in this resolution. See c++std-lib-9127. 
>      We may need to reopen this issue."

In any case, this is moot. As I tried to explain, nobody really cares these
days about those bind1st and bind2nd binders, in the CD1 C++0x are already in
an appendix, as deprecated features, with the exact resolution of issue DR 109
included, as we are doing.

> Unfortunately Google turns up nothing for "c++std-lib-9127" except this cryptic
> message, and just "9127" and other variations aren't productive either. Can you
> tell me where to find it?

It's a message to the ISO library reflector. Really, given the above, I would
suggest not wasting further time...


-- 


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


  parent reply	other threads:[~2008-10-13 16:24 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 [this message]
2008-10-13 17:03 ` igodard at pacbell dot net
2008-10-13 17:14 ` paolo dot carlini at oracle dot com
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=20081013162308.6861.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).