[fpc-devel] Interface delegation fix: backport to FPC 2.4.2 ...?

Marco van de Voort marcov at stack.nl
Wed May 19 17:36:11 CEST 2010

In our previous episode, Joost van der Sluis said:
> > System quo what where? The current libs are mainly about compatibility, and
> > because of that e.g. many language extensions from D4+ were never introduced
> > into the system (which is why e.g. the LCL uses TStrings instead of a
> > minimal interface needed to draw)
> I think I would agree with you if it was true that most libraries are
> about compatibility.

If not, why are we having this discussion about FPC specific enhancements
only 13 years after their introduction? (well, save for TFPList then)

Of course they are about compatibility. There is nothing else.

> But if I want to replace TComponent/TControl/TPersistent with newer
> versions, I would start copy-pasting them.

I don't see why the observer pattern is needed at such low level any more
than 20 other little handy features that each would be a lot easier if they
just had a field/property in the baseclasses.

It is the beginning of the end.

> And there would be only a few changes. (I can't think
> of any now, expect for adding the ability to use the observer pattern)

It is always only a few places. But what you are effectively doing is
opening the gate. 

If we allow this, the rest is only a matter of time. If you want to be the
library designer, do so, and do it well instead of applying bandaids to the
current classes.

More information about the fpc-devel mailing list