🚀 go-pugleaf

Hi Dick
I came to Interfaces due to the following.
In a more general class I had to store instances of classes with no
common ancestor (except of course Object).
So I used an Object to store them all.
At this point for the compiler all these instances (of different classes)
are Objects only and you are able to call methods of class Object only.
You have to cast your instances to a more specialized type
who knows the methods you want to call.
So I had ask each instance by using instanceof are of type A or type B
and so on, casted it to that type and were now able to call the method I
needed.
Then I realized that I wanted from all these instances nearly the same so
they all
implemented a method of the same name.
But this doesn't help you at this point.
Only if you let all your different classes implement an Interface that
requirers that method
to be defined you can throw away all these instanceof staments and cast all
these
different instances to that interface and call that method.
You can even store now all these instances under that interface and have not
to cast anymore.
Ok
a little bit bulky
Michael