public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: nathan@gcc.gnu.org To: nathan@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/164: bogus error throwing class with inaccessible base Date: Tue, 04 Dec 2001 01:56:00 -0000 [thread overview] Message-ID: <20011204095606.2946.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/164; it has been noted by GNATS. From: nathan@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, nathan@codesourcery.com, nathan@gcc.gnu.org Cc: Subject: Re: c++/164: bogus error throwing class with inaccessible base Date: 4 Dec 2001 09:49:58 -0000 Synopsis: bogus error throwing class with inaccessible base State-Changed-From-To: analyzed->closed State-Changed-By: nathan State-Changed-When: Tue Dec 4 01:49:56 2001 State-Changed-Why: 2001-12-04 Nathan Sidwell <nathan@codesourcery.com> PR g++/164 * init.c (sort_base_init): Allow binfos to be directly specified. * method.c (do_build_copy_constructor): Explicitly convert to the base instance. (do_build_assign_ref): Likewise. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=164&database=gcc
next reply other threads:[~2001-12-04 9:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-12-04 1:56 nathan [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-12-04 1:50 nathan 2001-11-16 18:26 nathan 2001-11-16 18:06 nathan
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=20011204095606.2946.qmail@sources.redhat.com \ --to=nathan@gcc.gnu.org \ --cc=gcc-prs@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: linkBe 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).