public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Uwe Seimet <us@orbacus.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/5297: operator!() const incorrect for fstream class
Date: Mon, 07 Jan 2002 06:36:00 -0000	[thread overview]
Message-ID: <20020107143601.19800.qmail@sources.redhat.com> (raw)

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

From: Uwe Seimet <us@orbacus.com>
To: Carlo Wood <carlo@alinoe.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/5297: operator!() const incorrect for fstream class
Date: Mon, 7 Jan 2002 15:29:39 +0100

 Hello Carlo,
 
 > >     fstream afile(MYNAME, ios::in|ios::out|ios::app);
 > >     assert(afile);
 > 
 > Did you mean:  assert(!afile);  ?
 
 Actually our code looks like this:
 
     fstream afile(m_asset_file, ios::in|ios::out|ios::app);
     if (!afile) {
         cerr << "Cannot open " << m_asset_file << endl;
         throw 0;
     }
 
 Even if the stream could be created I get the "Cannot open" message with gcc
 3.0.3. With other C++ compiler and also with gcc 2.95.3 everything is fine.
 !afile should evaluate to false, not to true, because operator!() const
 should return the result of fail(), as mandated by ISO C++, 27.4.4.3.
 
 Best regards,  Uwe
 
 -- 
 ----------------------------------------------------------------------------
  Dr. Uwe Seimet                                    mailto:us@orbacus.com
  IONA - END 2 ANYWHERE                             http://www.orbacus.com


             reply	other threads:[~2002-01-07 14:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-07  6:36 Uwe Seimet [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-08  8:16 Paolo Carlini
2002-01-08  6:36 Uwe Seimet
2002-01-07 13:46 paolo
2002-01-07  6:26 Carlo Wood
2002-01-07  5:46 us

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=20020107143601.19800.qmail@sources.redhat.com \
    --to=us@orbacus.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: 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).