>
>
>No, it's just saying you can't rely on detecting errors via isClosed(). You
>might see a spontaneous close after an error, but it's not *guaranteed* --
>only close() is guaranteed to cause isClosed() to return true.
>
>The next paragraph, which you trimmed, clarifies that:
>
Yes, that was the *next* paragraph abotu not relying on detecting errors.
This one explicitly said that it is *guaranteed* that isClosed() will
return true *only* after close() has been called.
And the previous one was - if the close() has been called *or* certain
fatal errors occured...
Dima