public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: swhite@discreet.com To: gcc-gnats@gcc.gnu.org Subject: c++/6340: copy constructor vs non-default constructor Date: Wed, 17 Apr 2002 12:16:00 -0000 [thread overview] Message-ID: <20020417191304.15535.qmail@sources.redhat.com> (raw) >Number: 6340 >Category: c++ >Synopsis: copy constructor vs non-default constructor >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed Apr 17 12:16:02 PDT 2002 >Closed-Date: >Last-Modified: >Originator: stephen white >Release: 3.02 >Organization: >Environment: red hat linux 7.1 kernel 2.4.2-2 >Description: the attached code generates the following error: foo.cpp: In function `int main (int, char **)': foo.cpp:16: `Thing2::Thing2 (const Thing2 &)' is private foo.cpp:25: within this context while the copy constructor is private, it should never be called. in fact, if it is made public, it *is* never called. it seems as if g++ just wants there to be a public copy constructor to give it a warm fuzzy feeling. the workaround is to use: Thing2 b( a ); >How-To-Repeat: g++ -lstdc++ foo.cpp >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: text/plain; name="foo.cpp" Content-Disposition: inline; filename="foo.cpp" #include <iostream.h> class Thing1 { }; class Thing2 { public: Thing2( const Thing1& r ) { cout << "constructing Thing2 from const Thing1&\n"; } private: Thing2( const Thing2& r ) { cout << "copy constructor (PROHIBITED)\n"; } }; int main(int argc, char **argv) { Thing1 a; Thing2 b = a; }
next reply other threads:[~2002-04-17 19:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-17 12:16 swhite [this message] 2002-04-18 0:58 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=20020417191304.15535.qmail@sources.redhat.com \ --to=swhite@discreet.com \ --cc=gcc-gnats@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).