Accessing derived class properties when implementing an interface method with abstract base class as parameter?

This is a clue that a design change might help. Your current interface says "I work on Foo s". If the implementation only works on Fum s, then you've got a mismatch in what you're saying and what you're doing.

If you're really only expecting Fum s, then declare the parameter in the interface as a Fum .

I think what you're doing is fine because Fum extends Foo you should be able to cast it in the way that you are.

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.

Related Questions


Thank You!
send