[Lazarus] Please define "delphi compatibility"

Marc Weustink marc.weustink at cuperus.nl
Wed Oct 10 16:33:50 CEST 2012

Bart wrote:
> On 10/10/12, Mark Morgan Lloyd <markMLl.lazarus at telemetry.co.uk> wrote:
>> As with most if not all open source projects, if we don't like it we can
>> fork off. However my own position is that I trust the core developers,
>> who are effectively defined by their understanding of how the code works.
> But then again, it would be nice for committers to know if extending
> an LCL component beyound it's Delphi's counterpart is considered to be
> "officially" OK (as long as the extension is considered usefull and
> meaningfull and not just fullfilling the needs of very few people (and
> there may be more criteria)).

We already have added extensions to LCL classes.

Things coming in mind are TGraphic and descendants. Or TImagelist, or ...

I see no reason we should limit ourselves to what Delphi has implemented 
(which version of Delphi)

Extensions are ok as long as they make sense and don't over complicate 
the component. (IIRC we have Control.SetSize(width, Height), while in 
delphi you need 2 calls)

> Getting back to the thread that stated this discussion:
> I could spend time and energy on implementing an ImageList for
> TDBNavigator (which Delphi doesn't have, and which maybe usefull for
> more than just a few people). But i would then become very frustrated
> if the patch was rejected because of "Delphi incompatibility".

I won't reject it, but I would depend on others to apply it


More information about the Lazarus mailing list