Geir Magnusson Jr wrote:
Well, I don't really know if Sun would do that. There is an expert
group that Sun has to deal with...
But if it did happen, yes, we'd have to fix our code.
I agree. Whatever experience I've had with java till now, I have found
that Sun mainly deprecates a method and provides a replacement, instead
of changing the spec for that method after the spec has been released.
So, if Sun decides to deprecate a method, it will still not break
harmony. I still feel our code should be spec compatible and not bug
compatible with Sun's impl. As a developer, I would look at the API docs
and then write the code. So, if our impl is compatible with the API
docs, won't that make a case for using harmony instead of a buggy impl :)
Thanks,
Mikhail
On 2/17/06, karan malhi <[EMAIL PROTECTED]> wrote:
Anton Avtamonov wrote:
IMHO, when spec states some exception we should be spec-compatible.
+1
On 2/17/06, Mikhail Loenko <[EMAIL PROTECTED]> wrote:
I agree with Tim that we should discuss on the dev list
+1
Later we might want to have some roadmap once we find a number
of similar issues
At this point I think we might be compatible when RI throws
wrong exceptions - for example it often mixes NPE and
IllegalArgumentException
Sometimes spec states IllegalArgumentException should be thrown, but
implementation produces NPE. I think that is because
IllegalArgumentException is missed in impl and algorithm just failed
somewhere...
IMHO, when spec states some exception we should be spec-compatible.
--
Anton Avtamonov,
Intel Middleware Products Division
--
Karan Singh
--
Karan Singh
