public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Craig Rodrigues <rodrigc@mediaone.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: libstdc++/4536 ostream seekp & istream seekg should scope failbit
Date: Sun, 14 Oct 2001 12:36:00 -0000	[thread overview]
Message-ID: <20011014193601.25841.qmail@sourceware.cygnus.com> (raw)

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

From: Craig Rodrigues <rodrigc@mediaone.net>
To: gcc-patches@gcc.gnu.org
Cc: libstdc++@gcc.gnu.org, gcc-gnats@gcc.gnu.org, brendan@zen.org,
   rodrigc@gcc.gnu.org
Subject: Re: libstdc++/4536 ostream seekp & istream seekg should scope failbit
Date: Sun, 14 Oct 2001 15:25:19 -0400

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=4536&database=gcc
 
 Hi,
 
 Following patch addresses PR 4536 on mainline.
 
 "ostream's seekp and istream's seekg methods need to use failbit as
 `ios_base::failbit'.
 It may be worth noting that the setting of failbit goes in line 
 with the change for library DR #129. The standard pre-DR edits 
 does not include the clause in $27.6.2.4(2) regarding the setting 
 of failbit."
 
 
 2001-10-11  Brendan Kehoe  <brendan@zen.org>
 
 	* bits/ostream.tcc (seekp): Scope use as ios_base::failbit.
 	* bits/istream.tcc (seekg): Likewise.
 
 Index: include/bits/ostream.tcc
 ===================================================================
 RCS file: /cvs/gcc/egcs/libstdc++-v3/include/bits/ostream.tcc,v
 retrieving revision 1.15
 diff -u -p -r1.15 ostream.tcc
 --- ostream.tcc	2001/09/25 23:51:17	1.15
 +++ ostream.tcc	2001/10/10 11:44:23
 @@ -346,7 +346,7 @@ namespace std 
        if (__sbin && __cerb)
  	__xtrct = __copy_streambufs(*this, __sbin, __sbout);
        if (!__sbin || !__xtrct)
 -	this->setstate(ios_base::failbit);
 +	this->setstate(ios_base::failbit);
        return *this;
      }
  
 Index: include/bits/istream.tcc
 ===================================================================
 RCS file: /cvs/gcc/egcs/libstdc++-v3/include/bits/istream.tcc,v
 retrieving revision 1.19
 diff -u -p -r1.19 istream.tcc
 --- istream.tcc	2001/09/25 23:51:17	1.19
 +++ istream.tcc	2001/10/10 11:44:13
 @@ -963,7 +963,7 @@ namespace std 
  
  // 129. Need error indication from seekp() and seekg()
  	      if (__err == pos_type(off_type(-1)))
 -		this->setstate(failbit);
 +		this->setstate(ios_base::failbit);
  #endif
  	    }
  	  catch(exception& __fail)
 @@ -996,7 +996,7 @@ namespace std 
  
  // 129. Need error indication from seekp() and seekg()
  	      if (__err == pos_type(off_type(-1)))
 -		this->setstate(failbit);
 +		this->setstate(ios_base::failbit);
  #endif
  	    }
  	  catch(exception& __fail)
 -- 
 Craig Rodrigues        
 http://www.gis.net/~craigr    
 rodrigc@mediaone.net          


             reply	other threads:[~2001-10-14 12:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-14 12:36 Craig Rodrigues [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-04  7:36 libstdc++/4536: " bkoz
2001-11-04  3:33 bkoz
2001-10-25 21:49 bkoz
2001-10-11  6:56 brendan

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=20011014193601.25841.qmail@sourceware.cygnus.com \
    --to=rodrigc@mediaone.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).