public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
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:46:00 -0000	[thread overview]
Message-ID: <20020805164602.29210.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/7498; it has been noted by GNATS.

From: Gabriel Dos Reis <gdr@integrable-solutions.net>
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: 05 Aug 2002 18:34:23 +0200

 mdp@fnal.gov writes:
 
 | >Number:         7498
 | >Category:       c++
 | >Synopsis:       copy constructor of ostream (and ios) is private and it should not be!
 
 [...]
 
 | >Release:        gcc 2.96.3 20000503/Linux
                   
 There is no GCC release named 2.96.3, I guess you meant 2.95.3.
 That release is known to come with pre-standard library.
 The library that comes with GCC-3.x is much more compliant and meets
 the standard requirement in that area.
 
 [...]
 
 |   ostream a=file;
 
 This is ill-formed, you cannot copy a std::ostream.
 
 | works on Visual C++ but on g++
 
 If it worked with Visual C++, then it is a bug in that compiler.
 
 -- Gaby


             reply	other threads:[~2002-08-05 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-05  9:46 Gabriel Dos Reis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-05  9:36 Phil Edwards
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=20020805164602.29210.qmail@sources.redhat.com \
    --to=gdr@integrable-solutions.net \
    --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).