public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "phil at mitre dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/26458] Passing a NULL char* into output stream now breaks the output stream Date: Fri, 24 Feb 2006 21:15:00 -0000 [thread overview] Message-ID: <20060224211424.15276.qmail@sourceware.org> (raw) In-Reply-To: <bug-26458-12260@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from phil at mitre dot org 2006-02-24 21:14 ------- Subject: RE: Passing a NULL char* into output stream now breaks the output stream Yup. But by providing the ability to batch stream inserts, per the standard I presume otherwise it's not much of a stream, then you create the situation where this difficulty exists. That's kinda why I joked about "filing a PR with the standard". If the standard says you can string together inserts, and that a failed insert will "disable" the stream until the error is cleared, but not allowing you to determine where an error occurred seems a failing of the standard. BTW, I thought that GNU was never one to limit themselves to a standard when they could always rise above it and do better. phil Phil Brown Lead Software Systems Engineer Mitre CAASD phil@mitre.org Perception is nine-tenths of the flaw. >-----Original Message----- >From: pcarlini at suse dot de [mailto:gcc-bugzilla@gcc.gnu.org] >Sent: Friday, February 24, 2006 4:03 PM >To: Brown, Phil >Subject: [Bug libstdc++/26458] Passing a NULL char* into >output stream now breaks the output stream > > > >------- Comment #8 from pcarlini at suse dot de 2006-02-24 >21:03 ------- >(In reply to comment #7) >> . In my recent example I was >> explaining how, even if I asserted ostream state and detected that an >> error had occurred, I would not be able to determine WHERE the error >> had occurred. > >Indeed, I understand, but this is a general "issue", which has >nothing to do >with the specific inserter. Any time you "batch" many >insertions you loose the >ability to do fine grained error checking, by definition. > > >-- > > >http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26458 > >------- You are receiving this mail because: ------- >You reported the bug, or are watching the reporter. > -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26458
next prev parent reply other threads:[~2006-02-24 21:14 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-02-24 16:53 [Bug c++/26458] New: " phil at mitre dot org 2006-02-24 17:25 ` [Bug libstdc++/26458] " pcarlini at suse dot de 2006-02-24 18:48 ` phil at mitre dot org 2006-02-24 18:55 ` phil at mitre dot org 2006-02-24 18:59 ` pinskia at gcc dot gnu dot org 2006-02-24 19:04 ` phil at mitre dot org 2006-02-24 20:40 ` pcarlini at suse dot de 2006-02-24 20:45 ` phil at mitre dot org 2006-02-24 21:04 ` pcarlini at suse dot de 2006-02-24 21:15 ` phil at mitre dot org [this message] 2006-02-24 21:32 ` pcarlini at suse dot de [not found] <bug-26458-4@http.gcc.gnu.org/bugzilla/> 2011-03-13 7:28 ` ian at airs dot com 2011-03-13 13:11 ` paolo.carlini at oracle dot com
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=20060224211424.15276.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: 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).