[fpc-devel] Interface delegation fix: backport to FPC 2.4.2 ...?
graemeg.lists at gmail.com
Wed May 19 17:26:36 CEST 2010
Marco van de Voort het geskryf:
> 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
You are totally over exaggerating. If FPC's only design goal is to be
compatible with Delphi, there is NO future for FPC. Surely FPC should be
open to new features and ideas to improve itself over competition - yet
keeping compatibility in mind but not limiting itself to the latter.
As for not many language extensions... Developers here are constantly told
it is simply because nobody is supplying patches for them. So what is it?
The Observer will NOT break any compatibility, has minimal impact on code
size or the class interface.
tiOPF went through the same process a couple of years ago. Everybody made a
big mountain of a problem about introducing Observer into one of it's most
used base classes. In the end it was implemented and 3 years down the line,
not a single person has every complained about it! In fact, more people
started using the Observer feature for other things and commented on how
handy it is. In tiOPF the internal list used by the Observer is only
created when needed, so hardly any extra memory was used - and yes my
programs loads about 50,000-80,000 objects and it did not affect our
systems at all. Peter H.'s software loads even more objects and he never
> If the status quo hurts so much, than start with a clean slate.
Starting a brand new class hierarchy is totally out of the question - that
would be like rewriting the whole RTL and FCL! To quote the famous Florian
saying: "you have no clue what you are talking about".
- Graeme -
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
More information about the fpc-devel