[Lazarus] Class autocompletion and abstract methods.
Torsten Bonde Christiansen
tc at epidata.dk
Thu Apr 15 11:30:31 CEST 2010
> > Lazarus core itself has such code. Earlier I tried to understand Designer,
> > ControlSelection and Object Inspector code.
>
> Yes, Lazarus has this "one big file" problem it and it is horrible.
> I tried to fix some parts of it, but my fixes were rejected due to
> backwards-compatibility concerns.
> This highlights yet another reason to design the code properly --
> after you create
> the big mess, you might not be able to untangle it even if you wanted to!
How would you fix it for Designer, ControlSelection and Object Inspector?
They are truly interdependent. It is not caused by poor design.
Juha
More information about the Lazarus
mailing list