On Wednesday, 30 October 2013 at 17:14:39 UTC, Uranuz wrote:
I think that I understand it now. If class A implements some
interface B it should implement all methods of interface B even
if they are abstract.
Yes.
Making abstract class itself can be useful if you have
implemented all its methods but still want it to be used only for
inheritance as making instances of abstract classes is
compile-time error. If there is at least on abstract method it
does not make any difference (other than documenting intention)
