Abstract methods cannot be final!!!!Really??

[Sri Jad]

as per K&B Book(1.4) from page 129

Abstract methods must be implemented by a subclass, so they must be
inheritable. For that reason:
❑ Abstract methods cannot be private.

❑ Abstract methods cannot be final.

But the following code works fine for me ..how come???

public abstract class Kalag {
abstract void method();
}

public class Kala extends Kalag {
final void method() {
}
}

[Jeroen T Wenting]

What happens when you implement an abstract method?
Can you call the method now in the class that implemented it?
What does that tell you about the abstractness of the method once in the implementing class?

[Keith Lynn]

Your example doesn't involve an abstract class that is final. Your example is a concrete class that inherits from an abstract class and makes its overridden method final.

Making a method final in a class does not make the class final.

However, making a method abstract in a class does make the class abstract.

[Sri Jad]

I got it

When author says

Abstract methods cannot be final.

that means

the following code doesn't work

public abstract final class Kalag {
  abstract void method();
}

Only public or protected are allowed..

[marc weber]

Originally posted by Sri Jad:
I got it...

Not quite. Take another look at the responses by Jeroen and Keith.

[Somesh Rathi]

Hi,
Method signature can't be abstract final.
Please correct me if i'm wrong.

[wise owen]

You are right.
"abstract methods cannot be declared private, static, final, native, strictfp or synchronized"

[Jeroen T Wenting]

And also think of the logic behind it.
What does final mean when applied to a method signature?
What does abstract mean to a method signature?

What would the combination therefore mean to a class in which such a method were declared?