On 1/30/11 8:23 PM, Steven Bethard wrote:
Anyway, I've given my best shot on this discussion, and I think we've
pretty much reached an impasse, where I'm more concerned about ease of
use and interop with other Java libraries and you're more concerned
about making it harder to accidentally write code that doesn't expect
all the exceptions that could arise from it.
I actually believe it is important to know what people do expect,
because they act according to that. If you use an Iterator you
do not expect the previously mentioned things, because they usually
do not occur when you use an Iterator. You say it is just an issue for
people
who do not read the documentation, yeah sure. But there are also people
who will later just read the source code and these readers would easily
get misguided, because things are different to what they used to be.
Could you at least document some version of this discussion (e.g. the
three valid points above) in the documentation for ObjectStream? That
way when future users think "gee it would be nice if this used the
Iterator API", they'll see immediately why you've chosen not to.
+1 that would be really nice, do you would like to contribute a patch ?
BTW, we have many places where we really could need some help,
in case you are interested. Maybe it is a bit boring, but most important
for our next release is the extension of our documentation. For example,
we are still
missing a good overview about the NLP tasks our components can solve.
Jörn
