next »

[Marvin Fröhlich]

When I applied the new HIAL API to the Xith codebase, I took great advantage of the @Override annotations, that are placed at all overridden methods inside of xith and xith-tk. You should configure your Eclipse to report a warning for missing annotations. It really helps. Anywhere, where the super method of an overridden and annotated method doesn't exist, a compile error is reported. So the IDE helps you to find all the places, where to change something and helps you to not miss one.

Marvin

['n ddrylliog]

And that's where you see the use of an "override" keyword, as in a Java-compatible language named "hellIdontrememberthename". The only problem with @Override annotations is that they are not mandatory (and they are only 1.5+),

[Marvin Fröhlich]

The only problem with @Override annotations is that they are not mandatory...

That's a problem for many parts of the fully backwards compatible Java language specifications. One day, they should cut off support for older versions.

...(and they are only 1.5+),

Well, that they're only 1.5+ is not a real problem. Who ever wants to use something older than 1.5 is not very wise or is forced to use it .

Marvin

['n ddrylliog]

...(and they are only 1.5+),

Well, that they're only 1.5+ is not a real problem. Who ever wants to use something older than 1.5 is not very wise or is forced to use it .

Well, compatibility issues, as always. (Apple power...)

[Marvin Fröhlich]

Well, compatibility issues, as always. (Apple power...)

I remember the discussions about Xith3D moving to Java-1.5 or not. And there was the argument, that there was not Java-1.5 support on Mac. But there actually was. So Xith moved to 1.5. So this is definitely not a problem.

Well, as far as I know, there's no Java-1.6 for Mac (Am I wrong?). But 1.5 exists.

Marvin

['n ddrylliog]

Hehe Then you forgot everyone still on 1.4.2 (there are a lot) or worse, on M$ JRE 1.1

[Marvin Fröhlich]

Hehe Then you forgot everyone still on 1.4.2 (there are a lot) or worse, on M$ JRE 1.1

Blame on M$! Stone them! Hunt them down!... Well, We don't have to and won't care about anybody using 1.1. And I guess, it is a half-compatible M$-Java-implementation, which is anyways meaningless.

If you want progress in an API and want to improve it, you sometimes need to abandon support for older versions. And I think, Sun should abandon the "direct" support for JREs older than 1.4 and once older than 1.5.

Marvin

[jeepndesert]

hmm, i'm requiring Java 1.6 in the jws for Mac users...oops...

['n ddrylliog]

Hehe Then you forgot everyone still on 1.4.2 (there are a lot) or worse, on M$ JRE 1.1

Blame on M$! Stone them! Hunt them down!... Well, We don't have to and won't care about anybody using 1.1. And I guess, it is a half-compatible M$-Java-implementation, which is anyways meaningless.

If you want progress in an API and want to improve it, you sometimes need to abandon support for older versions. And I think, Sun should abandon the "direct" support for JREs older than 1.4 and once older than 1.5.

Myeah, but users want support, too. About the M$ implementation, you're kinda generous with M$s when you say "half-compatible" maybe "quart-compatible" is even too much.

[Marvin Fröhlich]

About the M$ implementation, you're kinda generous with M$s when you say "half-compatible" maybe "quart-compatible" is even too much.

Yeah