Originally posted by Bruce Evans:
An abstract method can't say anything about its implementation.
That's true, Bruce, but, at the same time, I got this from the JLS:
The effect of the strictfp modifier is to make all float or double expressions within the class declaration be explicitly FP-strict (�15.4). This implies that all methods declared in the class, and all nested types declared in the class, are implicitly strictfp.
If that's the case, it would seem odd that you can declare a class to be strictfp (and therefore make all of its methods strictfp) but you can still declare one or more of those methods to be abstract. In essence, you've created an abstract, strictfp method. Doing so explicitly, however, produces a compiler error.
I must say that I never use the strictfp modifier so I'm not well versed in its usage, but there does seem to be, in my opinion, anyway, some degree of contradiction here.