public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Matthew Mueller <donut@azstarnet.com>
To: pme@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: libstdc++/2913
Date: Sat, 16 Jun 2001 21:36:00 -0000 [thread overview]
Message-ID: <20010617043602.7010.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR libstdc++/2913; it has been noted by GNATS.
From: Matthew Mueller <donut@azstarnet.com>
To: pme@gcc.gnu.org
Cc: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: libstdc++/2913
Date: Sat, 16 Jun 2001 21:29:27 -0700
I didn't mean to suggest that it should check individual errors, just
that it is ignoring this (and probably all) errors in a certain case.
If you compare our results, I think the reason is apparent. Your test
returns error on both the write and the file close. My test with 2.95
returned error only on close, likely due to buffering issues. So my
theory is that in 3.0 the error is not checked when closing the file,
only on writing it. Due to buffering, fclose(3) return value must be
checked for errors too.
--
Matthew Mueller
donut@azstarnet.com
next reply other threads:[~2001-06-16 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-16 21:36 Matthew Mueller [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-16 23:55 libstdc++/2913 Phil Edwards
2001-11-16 23:46 libstdc++/2913 Brad Garcia
2001-06-06 16:56 libstdc++/2913 pme
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=20010617043602.7010.qmail@sourceware.cygnus.com \
--to=donut@azstarnet.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=pme@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).