Jing LV wrote:
Thanks for reply Alan, sorry didn't see this mail before I raise an
issue on https://bugs.openjdk.java.net/show_bug.cgi?id=100169 (my mail
server seems some problem these days)
Consider it is using underlying writer, one thing I need to mention is
that in the testcase I post in
Thanks for reply Alan, sorry didn't see this mail before I raise an
issue on https://bugs.openjdk.java.net/show_bug.cgi?id=100169 (my mail
server seems some problem these days)
Consider it is using underlying writer, one thing I need to mention is
that in the testcase I post in the first mail,
Jing LV wrote:
Hi Alan,
(Sorry for late reply that it seems my mail-box has some trouble that
I cannot send my mail yesterday). I agreed with you that the document
may be changed. However as you see another problem is that the write
method is unstable, it may or may not throw the exception, o
δΊ 2011-1-26 0:19, Alan Bateman ει:
Jing LV wrote:
Hello,
I find a problem in java.io.BufferedWriter. It is stated in the java
spec of its close() method:
"... Once the stream has been closed, further write() or flush()
invocations will cause an IOException to be thrown."
However if a BufferedWr
Jing LV wrote:
Hello,
I find a problem in java.io.BufferedWriter. It is stated in the java
spec of its close() method:
"... Once the stream has been closed, further write() or flush()
invocations will cause an IOException to be thrown."
However if a BufferedWriter is created with a delegated wri
Hello,
I find a problem in java.io.BufferedWriter. It is stated in the java
spec of its close() method:
"... Once the stream has been closed, further write() or flush()
invocations will cause an IOException to be thrown."
However if a BufferedWriter is created with a delegated writer, then it
seem
