On 11/03/2015 18:25, Brian Burkhalter wrote:
Hello,
This message is a mere reprise of this reminder
http://mail.openjdk.java.net/pipermail/core-libs-dev/2015-February/031848.html
from February 25. The original review thread on this topic went through to its
conclusion but some alternatives arose and there has been no definitive
outcome. It would be good to clear this up at last.
One option not mentioned in the above-linked message would be to resolve the
issue as already approved and then file another one covering any change to the
approach, such as listed in choices B and C in the foregoing.
If put throws IAE for an invalid key name then having get and remove do
the same would be consistent. As the NUL case is a corner case and
preferences don't seem to be widely used then I would think the
compatibility impact of the IAE in a major release wouldn't be too
significant. I think it should be okay to do it in a follow-on bug if
that makes it easier.
-Alan
