--- 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 c
--- Comment #7 from phil at mitre dot org 2006-02-24 20:40 ---
Subject: RE: Passing a NULL char* into output stream now breaks the output
stream
Agreed, the stream object itself hopfully doesn't get corrupted (bad),
but what I was refering to was "the data" itself,
--- Comment #5 from phil at mitre dot org 2006-02-24 19:00 ---
(In reply to comment #4)
> I think Paolo forgot to mention this is required by the C++ standard.
Well that's different then. I realize that many non-standard things were
allowed pre gcc-3.0 and that 3+ was sta
--- Comment #3 from phil at mitre dot org 2006-02-24 18:54 ---
See comment #2.
--
phil at mitre dot org changed:
What|Removed |Added
Status|RESOLVED
--- Comment #2 from phil at mitre dot org 2006-02-24 18:45 ---
Subject: RE: Passing a NULL char* into output stream now breaks the output
stream
Thanks for the quick response. This came up when some old systems were
ported from Solaris using gcc-2.9.5 or so and out output files just
nto output stream now breaks the
output stream
Product: gcc
Version: 3.2.3
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: phil at mi
