Why would you need to know whether a method of an abstract class is abstract?

You need to know what methods are abstract because you will need to provide implementations for those methods when inheriting the class.

2 Either providing an implementation or declaring it abstract again... – Tommy May 13 '11 at 9:30 1 @Tommy: Better say, provide an implementation or declare the implementing class abstract. – Adeel Ansari May 13 '11 at 9:36.

As an extension to Fredrik's answer, it also specifies which behaviour is intended to be changed. You can usually override a method (if the method is not final and the class is not final) but in practice that can be very tricky if the class is not specifically designed for changes. It may be that existing methods assume some kind of behaviour of the method you override, which is not specified (it happens) and that you do not provide.By explicitly declaring a method to be abstract you express the intention that the method will be implemented by someone else.

It also usually means that the documentation of an abstract method is a bit more complete with regards to expected behaviour.

If you call the abstract method you need to take into account that the actual implementation is elsewhere and may have some variation in behavior.

You have know if the method is abstract, because in that case you have to implement it in your concrete (inherited) class. I advice you to take a look on the following books about Design Patterns, because they mention these stuff and have practices too: oreilly.com/catalog/9780596007126.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.