public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gdr at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/24702] Koenig found functoid ref, but "cannot be used as a function"
Date: Sun, 04 Dec 2005 05:09:00 -0000	[thread overview]
Message-ID: <20051204050946.18080.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24702-11665@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from gdr at gcc dot gnu dot org  2005-12-04 05:09 -------
this issue should be resolved one way of the other based on the
core issue about argument dependent lookup specification, when a
non-function is found.  The "obvious" solution would be to do overload
resolution based on the signatures (whether actual function, constructor, 
function objects, or references to those).  However, all that needs
tracking the open core issue.


-- 

gdr at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gdr at gcc dot gnu dot org
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2005-12-04 05:09:46
               date|                            |


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


  parent reply	other threads:[~2005-12-04  5:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-07  7:09 [Bug c++/24702] New: " pierhyth at gmail dot com
2005-11-07 13:37 ` [Bug c++/24702] " pinskia at gcc dot gnu dot org
2005-11-09  1:33 ` pierhyth at gmail dot com
2005-11-16 19:28 ` gdr at integrable-solutions dot net
2005-12-04  5:09 ` gdr at gcc dot gnu dot org [this message]
     [not found] <bug-24702-4@http.gcc.gnu.org/bugzilla/>
2013-09-05 14:29 ` paolo.carlini at oracle dot com
2013-09-05 14:40 ` redi at gcc dot gnu.org
2013-09-05 14:43 ` redi at gcc dot gnu.org
2013-09-05 15:18 ` paolo.carlini at oracle dot com
2013-09-06  1:19 ` pierhyth at gmail dot com
2013-09-06  7:30 ` redi at gcc dot gnu.org

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=20051204050946.18080.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).