> > If you meant having many libs of different version exist
> side-by-side,
> > .NET runtime supports it, but Win32 itself doesn't
>
> Most unixes also have it. The point is that it kind of
> defeats the purpose.
> Having 20+ libraries called fpcrtl-xyz.dll (or
> fpcrtl.so.x.y.z on unixes) de
> That this requires a strict versioning schedule, is part of the deal.
> Borland's packages are also incompatible between released versions.
Which is very bad practice for a commercial IDE (makes third-party
commercial components support only some versions of Delphi [had suggested to
Borland to
> You can't, for Lazarus. You need the classes, that's what you
> need the plugins for in the first place: to install
> additional components on the component palette. They must
> descend from the TComponent which is in the IDE.
>
> There is no way around it.
If you had an immutable Icomponen
> > So, a component that you place in the component palette implements
> > some kind of "palette" interface, providing the IDE with the
> > communications it needs to work with the component.
>
> Nice idea, but I think you'll end up creating a set of
> interfaces which describes completely
> T
Op Fri, 9 Feb 2007, schreef George Birbilis:
> Speaking of namespaces, Borland added concept (to support .NET) in latest
> Delphis I think, has FPC done similar yet? Could help in this case
It is on the "not to be supported" list (unless we have to decide to be
Delphi .NET compatible). It won'
> Speaking of namespaces, Borland added concept (to support .NET) in latest
> Delphis I think, has FPC done similar yet? Could help in this case
We already have units, with etc? Maybe you want internal units ?
___
fpc-devel maillist - fpc-devel@lists.
Op Fri, 9 Feb 2007, schreef George Birbilis:
> don't take Borland as an example in this case, it's a very bad practice what
> they did...
I wouldn't go that far; solving OOP binary compatibility is hard and
Borland did contribute to the solution by including interfaces into the
language, but
Hi,
I want to include memory checking in my test application without having the
debuginfo (since that makes the application 10 times as big and takes longer to
compile).
Even without debuginfo it gives information, about the number of allocated memory
blocks that are not freed and whether so
