JDK-8067661: transferTo proposal for Appendable

Patrick Reinhart patrick at reini.net
Wed Nov 15 19:55:41 UTC 2017

Just to see if I picked up the Discussion so far. The discussion is
about that original sentence
from: http://cr.openjdk.java.net/~reinhapa/reviews/8067661/webrev.03

"Depending on which class implements the appendable, there may be a
limit of data
that can written to which in turn could lead to an exception."

And your current suggestion would look like:

1) "If the destination is capacity bounded and has insufficient capacity
to append all characters
read from the source then the exception may be thrown after transferring
some characters
to the destination"

At the version from:
I got the version from Brian Burkhalter suggested earlier:

2) "Note that it is possible an implementing class may limit the number of
characters which may be transferred and throw an exception if this limit
is exceeded."

Now looking at both versions, the version 1 seems a bit more declarative
than version 2 and I
would go for the first one...


Am 15.11.2017 um 19:07 schrieb Brian Burkhalter:
> On Nov 15, 2017, at 3:22 AM, Alan Bateman <Alan.Bateman at oracle.com
> <mailto:Alan.Bateman at oracle.com>> wrote:
>> .
> Could “is capacity-bounded and” be removed?
> Brian

More information about the core-libs-dev mailing list