public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kemin dot zhou at ferring dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/17611] ifstream could not read multiple files
Date: Thu, 23 Sep 2004 02:08:00 -0000	[thread overview]
Message-ID: <20040923020814.28120.qmail@sourceware.org> (raw)
In-Reply-To: <20040922153153.17611.kemin.zhou@ferring.com>


------- Additional Comments From kemin dot zhou at ferring dot com  2004-09-23 02:08 -------
Subject: Re:  ifstream could not read multiple files

pcarlini at suse dot de wrote:

>------- Additional Comments From pcarlini at suse dot de  2004-09-22 15:55 -------
>Not a bug, very well known, by the way, see:
>
>  http://gcc.gnu.org/onlinedocs/libstdc++/faq/index.html#4_4_iostreamclear
>
>The standard in force, as also clarifed by the resolution of DR22, does **not**
>say that open clears the flags!
>
>  
>
Thanks a lot.  Well, some other compilers has the ability to ability to 
open multiple files.  Maybe we should change
the standard.  I am not sure what is the benefit for leaving in the bad 
state even after a close and re.open operation.
But this is a minor thing I can live with. 

Kemin



**********************************************************************
Proprietary or confidential information belonging to Ferring Holding SA or to one of its affiliated companies may be contained in the message. If you are not the addressee indicated in this message (or responsible for the delivery of the message to such person), please do not copy or deliver this message to anyone. In such case, please destroy this message and notify the sender by reply e-mail. Please advise the sender immediately if you or your employer do not consent to e-mail for messages of this kind. Opinions, conclusions and other information in this message represent the opinion of the sender and do not necessarily represent or reflect the views and opinions of Ferring.
**********************************************************************



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17611


      parent reply	other threads:[~2004-09-23  2:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-22 15:32 [Bug c++/17611] New: " kemin dot zhou at ferring dot com
2004-09-22 15:44 ` [Bug libstdc++/17611] " bangerth at dealii dot org
2004-09-22 15:55 ` pcarlini at suse dot de
2004-09-23  2:08 ` kemin dot zhou at ferring dot com [this message]

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=20040923020814.28120.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).