public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: frank6thursday@aol.com, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: c++/9807: Derived class object used as default parameter for base class reference requires explicit cast to reference to base class
Date: Wed, 05 Mar 2003 22:06:00 -0000	[thread overview]
Message-ID: <20030305220650.20186.qmail@sources.redhat.com> (raw)

Synopsis: Derived class object used as default parameter for base class reference requires explicit cast to reference to base class

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Wed Mar  5 22:06:50 2003
State-Changed-Why:
    Confirmed. I think the compiler should accept this, but 
    no version of gcc does that. It works, though, if the
    reference parameter is constant.
    
    Here's a smaller code:
    ----------------------
    struct A {
        virtual ~A();
    };
    struct B : A {};
    
    struct C {
      C(A& a = B()){}
    };
    C c;
    ------------------------
    
    This is what I get:
    g/x> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c x.cc
    x.cc:9: error: could not convert `B()' to `A&'
    x.cc:7: error: in passing argument 1 of `C::C(A&)'
    
    There's something more weird: If I remove the virtual 
    destructor, then I get the following error message:
    g/x> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c x.cc
    x.cc:9: error: could not convert `{}' to `A&'
                                     ^^^^
                                     !!!!
    x.cc:7: error: in passing argument 1 of `C::C(A&)'
    
    That looks like real bogus!
    
    W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9807


             reply	other threads:[~2003-03-05 22:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05 22:06 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-22 19:46 frank6thursday

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=20030305220650.20186.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=frank6thursday@aol.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).