public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: kawai@tkpe1.sumitomo-chem.co.jp
To: gcc-gnats@gcc.gnu.org
Subject: c++/9648: g++-3.2.2 cannot create a new file. (g++-2.95.3 does)
Date: Mon, 10 Feb 2003 20:16:00 -0000	[thread overview]
Message-ID: <20030210200607.1932.qmail@sources.redhat.com> (raw)


>Number:         9648
>Category:       c++
>Synopsis:       g++-3.2.2 cannot create a new file. (g++-2.95.3 does)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Mon Feb 10 20:16:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Takashi Kawai
>Release:        gcc-3.2.2, --enable-shared
>Organization:
>Environment:
Redhat Linux 7.2J, Dell PE2450 (Pentium III 1GHz x 2)
>Description:
The file "$HOME/foo.bar" should be opened whether it exists or not.  g++-2.95.3 works, however g++-3.22 doesn't work when the file doesn't exist; it says "cannot open /home/kawai/foo.bar"

>How-To-Repeat:
using namespace std;

#include <cstdlib>
#include <iostream>
#include <fstream>
#include <string>

int main(void)
{
string filename(getenv("HOME"));
filename += "/foo.bar";

std::fstream foo;
foo.open(filename.c_str(),ios::in | ios::out);

if (!foo) {
    cerr << "Cannot open " << filename << endl;
} else {
    cerr << "successfully opened " << filename << endl;
}

foo.close();

return 0;
}
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-02-10 20:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-10 20:16 kawai [this message]
2003-02-10 20:26 Takashi 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=20030210200607.1932.qmail@sources.redhat.com \
    --to=kawai@tkpe1.sumitomo-chem.co.jp \
    --cc=gcc-gnats@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).