[fpc-pascal] about interface and multiple inheritance

Marco van de Voort marcov at stack.nl
Wed Feb 25 10:40:53 CET 2015

In our previous episode, Michael Schnell said:
> > Exactly. Interface delegation solves this problem, that is why it was 
> > invented.
> How does this correspond to the fact that (AFAIK) interfaces are 
> auto-creating, reference-counted and auto-destroying, while classes are 
> not ?
> Ore is this just an unrelated additional feature of interfaces ?

Reference counted and thus auto destroying. They are not autocreating.

Note that interfaces does not necessarily map to the native class type. 

Strictly speaking it is possible to have interfaces to some external entity
that does not map to the own class type.

More information about the fpc-pascal mailing list