flush()not unformatted function
Section: 184.108.40.206 [ostream.unformatted] Status: CD1 Submitter: Martin Sebor Opened: 2006-06-14 Last modified: 2016-02-10
Priority: Not Prioritized
View all other issues in [ostream.unformatted].
View all issues with CD1 status.
The resolution of issue 60 changed
so as not to require it to behave as an unformatted output function.
That has at least two in my opinion problematic consequences:
flush() now calls
unconditionally, without regard to the state of the stream. I can't
think of any reason why
flush() should behave differently
from the vast majority of stream functions in this respect.
flush() is not required to catch exceptions from
pubsync() or set
badbit in response to such
events. That doesn't seem right either, as most other stream functions
I propose to revert the resolution of issue 60 with respect to
flush(). Specifically, I propose to change 220.127.116.11, p7
rdbuf() is not a null
rdbuf()->pubsync(). If that function returns
setstate(badbit) (which may throw
not behave as an unformatted output function (as described in
18.104.22.168, paragraph 1).
[ Kona (2007): Proposed Disposition: Ready ]