public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/7498: copy constructor of ostream (and ios) is private and it should not be! Date: Mon, 05 Aug 2002 09:36:00 -0000 [thread overview] Message-ID: <20020805163601.24929.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7498; it has been noted by GNATS. From: Phil Edwards <phil@jaj.com> To: mdp@fnal.gov Cc: gcc-gnats@gcc.gnu.org Subject: Re: c++/7498: copy constructor of ostream (and ios) is private and it should not be! Date: Mon, 5 Aug 2002 12:35:08 -0400 On Mon, Aug 05, 2002 at 04:22:39PM -0000, mdp@fnal.gov wrote: > The following program: > ----------------------------- > #include "iostream" > #include "fstream" > void main() { > ofstream file("test.dat"); > ostream a=file; > a << "Hello\n"; > file.close(); > } > ----------------------------- > > works on Visual C++ Visual C++ is broken. > but on g++ > gives the following error: Because the code is invalid. > Copy constructors of base_ios and derived classes should be public. No they shouldn't. See section 27.4 of the C++ standard. -- If ye love wealth greater than liberty, the tranquility of servitude greater than the animating contest for freedom, go home and leave us in peace. We seek not your counsel, nor your arms. Crouch down and lick the hand that feeds you; and may posterity forget that ye were our countrymen. - Samuel Adams
next reply other threads:[~2002-08-05 16:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-05 9:36 Phil Edwards [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-08-05 9:46 Gabriel Dos Reis 2002-08-05 9:35 pme 2002-08-05 9:26 mdp
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=20020805163601.24929.qmail@sources.redhat.com \ --to=phil@jaj.com \ --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: 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).