public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Rupert Wood" <me@rupey.net>
To: <bjensen@fastmail.fm>, "'Andrey Pozdeev'" <AndreyPozdeev@rambler.ru>
Cc: <gcc-help@gcc.gnu.org>
Subject: RE: Problem with overloaded function selection
Date: Mon, 12 Aug 2002 07:07:00 -0000	[thread overview]
Message-ID: <616BE6A276E3714788D2AC35C40CD18D5EC576@whale.softwire.co.uk> (raw)
In-Reply-To: <616BE6A276E3714788D2AC35C40CD18D780D92@whale.softwire.co.uk>

Bjorn Rhode Jensen wrote:

>  I guess, one will have to look in the specs to
> see, who is right in this matter. My gut feeling
> is, that it gcc is right. Conversions and function
> overloading seem pretty othogonal to me. Why should
> two conversions be worse than one conversion in matching
> an overloaded function??

I haven't had a chance to look at the standards either but I did play
with this a little: if you make test accept an A reference instead of an
A object:

    void test(A&) {}

then the GCC problem goes away. I guess the copy construction counts as
a second conversion.

Rup.

       reply	other threads:[~2002-08-12 14:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <616BE6A276E3714788D2AC35C40CD18D780D92@whale.softwire.co.uk>
2002-08-12  7:07 ` Rupert Wood [this message]
2002-08-12  7:13   ` bjorn rohde jensen
2002-08-12  3:25 Andrey Pozdeev
2002-08-12  7:01 ` bjorn rohde jensen
  -- strict thread matches above, loose matches on Subject: below --
2002-08-12  3:22 Andrey Pozdeev
2002-08-12  3:18 Andrey Pozdeev

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=616BE6A276E3714788D2AC35C40CD18D5EC576@whale.softwire.co.uk \
    --to=me@rupey.net \
    --cc=AndreyPozdeev@rambler.ru \
    --cc=bjensen@fastmail.fm \
    --cc=gcc-help@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).