Hi Alan,
I see the status of 7015589 has changed to fix delivered, so
is this fix in the repository(java8?) already?
On 2011/8/9 19:43, Alan Bateman wrote:
A few months back there was a bug report [1] pointing out that it's
possible to continue writing to a BufferedWriter after
I see that CR 7015589 was integrated into JDK8 b04.
-Chris.
On 09/22/11 09:40 AM, Jing Lv wrote:
Hi Alan,
I see the status of 7015589 has changed to fix delivered, so is this
fix in the repository(java8?) already?
On 2011/8/9 19:43, Alan Bateman wrote:
A few months back there was a bug
Jing Lv wrote:
Hi Alan,
I see the status of 7015589 has changed to fix delivered, so
is this fix in the repository(java8?) already?
Yes, it's been in the jdk8 for several weeks:
http://hg.openjdk.java.net/jdk8/jdk8/jdk/rev/759aa847dcaf
Changeset: 759aa847dcaf
Author:alanb
Date: 2011-08-18 16:47 +0100
URL: http://hg.openjdk.java.net/jdk8/tl/jdk/rev/759aa847dcaf
7015589: (spec) BufferedWriter.close leaves stream open if close of underlying
Writer fails
Reviewed-by: forax, mduigou
! src/share/classes/java/io
A few months back there was a bug report [1] pointing out that it's
possible to continue writing to a BufferedWriter after invoking its
close method and the close fails. A similar issue arises with
BufferedOutputStream and other classes. At issue is whether a stream (or
more generally a
On 08/09/2011 01:43 PM, Alan Bateman wrote:
A few months back there was a bug report [1] pointing out that it's
possible to continue writing to a BufferedWriter after invoking its
close method and the close fails. A similar issue arises with
BufferedOutputStream and other classes. At issue
This change looks good. I don't believe a compatibility switch for the
FilterOutputStream is warranted.
On Aug 9 2011, at 04:43 , Alan Bateman wrote:
A few months back there was a bug report [1] pointing out that it's possible
to continue writing to a BufferedWriter after invoking its
