Steve Loughran wrote:
Jesse Glick wrote:
Jess Holle wrote:
We've seen this before where A depends on B which /internally/
depends upon C and then suddenly one has to have C around to compile A.
Although this is not forbidden by the JLS (as far as I know), it does
seem undesirable. If you know of particular examples which can be
expressed as minimal test cases, I would encourage you to file bug
reports for the compiler.
Not ever seen that.
I have just been burned today by the fact that Java6 lets you do an
@Overrides on any method that implements an interface; I'd been using
that to indicate which methods were interface implementations. Java5
says @Overrides is only for non-abstract methods, hence breaks.
Yes, that's a really obnoxious failing in Java 5.
It's good that it was fixed in Java 6. It would have been even better
if it had been fixed in a Java 5 update.
--
Jess Holle
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
