On 05/12/2014 14:04, Chris Hegarty wrote:
On 05/12/14 11:38, Pavel Rappo wrote:
+1, I couldn’t say better
Right. This bug should only try to address the change in behavior that
was inadvertently introduced by 7015589[1][2].
I don't see any reason to make 'closed' protected ( part of the public
Java SE API ), something like:
Right, no need for it to be protected. I think what you have seems right
but we probably need a small spec clarification so that it reads "When
not already closed, the close method of FilterOutputStream ...". That
removes the testable assertion that flush that is always called.
-Alan
