Is the wrong version of the db.pas in fixes_3_2 branch?
The current version of db.pas in fixes_3_2 seems to be from the 3.3.1 branch
instead of the 3.2.3 branch.
The 3.3.1 db.pas adds a new enum value ftSingle to TFieldType.
This causes the compilation of ZeosDb 8.0 ZAbstractRODataset.pas to fa
On 15/03/2025 14:07, Jonas Maebe via fpc-devel wrote:
On 23/02/2025 14:22, Jonas Maebe via fpc-devel wrote:
On 23/02/2025 13:56, wkitty42--- via fpc-devel wrote:
FWIW: instead of rejecting, i would drop... that way their networking
stack has to wait on timeouts and adds a delay load to their
Michael Roland via fpc-devel schrieb am
Di., 1. Apr. 2025, 02:24:
> Is the wrong version of the db.pas in fixes_3_2 branch?
>
No.
>
>
> The current version of db.pas in fixes_3_2 seems to be from the 3.3.1
> branch instead of the 3.2.3 branch.
>
There have been changes from 3.3.1 that have bee
Hello Michael,
this has been fixed in the 8.0-patches branch of Zeos. Please check the SVN:
https://sourceforge.net/p/zeoslib/code-0/HEAD/tree/branches/8.0-patches/
or GIT repository:
https://github.com/marsupilami79/zeoslib/tree/8.0-patches
Zeos 8.0, as you can download it, is only meant for FP
On 05/04/2025 13:27, Sven Barth via fpc-devel wrote:
This is called contra-variance and is in general not something that
programming languages support. See for example here:
https://stackoverflow.com/questions/2995926/why-is-there-no-parameter-contra-variance-for-overriding
Thanks.
I hadn't
Martin Frb via fpc-devel schrieb am Sa.,
5. Apr. 2025, 12:02:
> See the below code. (tested 3.2.3 and 3.3.1)
>
> Is this intentionally allowed?
>
> Technically it should work. TSubTest.Test always returns something that
> fits the inherited requirement.
>
>
> program Project1;
> type
>TFoo =
On 03/04/2025 13:52, Martin Frb via fpc-devel wrote:
On 27/03/2025 12:28, Martin Frb wrote:
There are 2 features, I am missing.
I did a couple of experiments... Those are not finished code. They
only showcase the ideas, and only for the one OpenAddressingLp case
https://gitlab.com/martin_fr
See the below code. (tested 3.2.3 and 3.3.1)
Is this intentionally allowed?
Technically it should work. TSubTest.Test always returns something that
fits the inherited requirement.
program Project1;
type
TFoo = class end;
TBar = class(TFoo) end;
TTest = class
function Test: TFoo; v