https://bz.apache.org/bugzilla/show_bug.cgi?id=59634
Dominik Stadler <dominik.stad...@gmx.at> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Dominik Stadler <dominik.stad...@gmx.at> ---
The JavaDoc was partly updated in r1749213 and further refined in r1753912 to
state that the close() call may also invalidate other things and should only be
called before work with the object is done.
I have also removed the "has no effect on newly created... ", as I don't think
we should limit ourselves this way here, we should be able to do optimizations
in the future which make use of this. All other Java Closables do it this way
and thus let's do the same here.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org
