public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Takashi Kawai <kawai@tkpe1.sumitomo-chem.co.jp> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/9648: g++-3.2.2 cannot create a new file. (g++-2.95.3 does) Date: Mon, 10 Feb 2003 20:26:00 -0000 [thread overview] Message-ID: <20030210202601.15685.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/9648; it has been noted by GNATS. From: Takashi Kawai <kawai@tkpe1.sumitomo-chem.co.jp> To: gcc-gnats@gcc.gnu.org Cc: kawai@tkpe1.sumitomo-chem.co.jp (Takashi Kawai) Subject: Re: c++/9648: g++-3.2.2 cannot create a new file. (g++-2.95.3 does) Date: Tue, 11 Feb 2003 05:23:15 +0900 (JST) February 11, 2003 I'm sorry. The code is wrong and g++-3.22 is exactly correct. If the line: > foo.open(filename.c_str(),ios::in | ios::out); is replaced to: > foo.open(filename.c_str(),ios::in | ios::out | ios::trunc) , then it works. I'd completely misunderstood that "ios::in | ios::out" works even if the file doesn't exist; in fact, it doesn't work only when the file exists. I'm very sorry to bother you about my mistake. Best wishes, Takashi Kawai Takatsuki / Japan > Thank you very much for your problem report. > It has the internal identification `c++/9648'. > The individual assigned to look at your > report is: unassigned. > > >Category: c++ > >Responsible: unassigned > >Synopsis: g++-3.2.2 cannot create a new file. (g++-2.95.3 does) > >Arrival-Date: Mon Feb 10 20:16:00 UTC 2003 >
next reply other threads:[~2003-02-10 20:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-10 20:26 Takashi Kawai [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-10 20:16 kawai
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=20030210202601.15685.qmail@sources.redhat.com \ --to=kawai@tkpe1.sumitomo-chem.co.jp \ --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).