------- 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
[EMAIL PROTECTED]
Perception is nine-tenths of the flaw.
>-----Original Message-----
>From: pcarlini at suse dot de [mailto:[EMAIL PROTECTED]
>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
