On 13.11.2020 21:23, Juha Manninen via lazarus wrote:
On Fri, Nov 13, 2020 at 6:19 PM Larry Dalton via lazarus
mailto:lazarus@lists.lazarus-ide.org>>
wrote:
So we lose some backwards portability?
IIRC it has been called "forward compatibility" as opposed to
"backward compatibility".
On 13.11.2020 22:37, Michael Van Canneyt via lazarus wrote:
On Fri, 13 Nov 2020, Ondrej Pokorny via lazarus wrote:
Usually we try to use the "default" feature of the newly added
properties so that they are streamed only when really set and used.
When they are not used, the LFM can still be
Michael Van Canneyt via lazarus schrieb am
Fr., 13. Nov. 2020, 22:37:
>
>
> On Fri, 13 Nov 2020, Ondrej Pokorny via lazarus wrote:
>
> > Usually we try to use the "default" feature of the newly added
> properties so
> > that they are streamed only when really set and used. When they are not
>
On Fri, 13 Nov 2020, Ondrej Pokorny via lazarus wrote:
Usually we try to use the "default" feature of the newly added properties so
that they are streamed only when really set and used. When they are not used,
the LFM can still be loaded in a legacy version of Lazarus because the new
On Fri, Nov 13, 2020 at 6:19 PM Larry Dalton via lazarus <
lazarus@lists.lazarus-ide.org> wrote:
> So we lose some backwards portability?
>
IIRC it has been called "forward compatibility" as opposed to "backward
compatibility".
Backward compatibility means your old code works in new versions of
Usually we try to use the "default" feature of the newly added
properties so that they are streamed only when really set and used. When
they are not used, the LFM can still be loaded in a legacy version of
Lazarus because the new properties are not streamed.
Ondrej
On 13.11.2020 17:47,
This problem was brought to light when I couldn’t get 2.0.10 apps to hook up to
MySQL on Windows. I have no problem on my Linux box.
Sent from my iPhone
> On Nov 13, 2020, at 11:34, Michał Gawrycki
> wrote:
>
> Remove this property from lfm file and set it by code if needed (maybe along
>
Yes, but that's always so when properties are added to components.
Michael.
On Fri, 13 Nov 2020, Larry Dalton wrote:
So we lose some backwards portability?
Sent from my iPhone
On Nov 13, 2020, at 11:06, Michael Van Canneyt wrote:
Your .lfm file contains a property "autocommit" that
So we lose some backwards portability?
Sent from my iPhone
> On Nov 13, 2020, at 11:06, Michael Van Canneyt wrote:
>
>
> Your .lfm file contains a property "autocommit" that exists in 2.0.10 but not
> in 2.0.6.
> I think 2.0.10 is based on FPC 3.2.0 and 2.0.6 was still based on 3.0.4.
>
>
Your .lfm file contains a property "autocommit" that exists in 2.0.10 but not
in 2.0.6.
I think 2.0.10 is based on FPC 3.2.0 and 2.0.6 was still based on 3.0.4.
A lot of new properties appeared between 3.0.4 and 3.2.0.
Michael.
On Fri, 13 Nov 2020, Larry Dalton via lazarus wrote:
I forgot
I forgot to add that it compiles correctly, but then I get the runtime error
Sent from my iPhone
> On Nov 13, 2020, at 11:02, Larry Dalton wrote:
>
> This is only when I try to compile on Lazarus 2.0.6 on Windows. The project
> works fine on 2.0.10 on Linux. Any ideas?
>
> Sent from my
This is only when I try to compile on Lazarus 2.0.6 on Windows. The project
works fine on 2.0.10 on Linux. Any ideas?
Sent from my iPhone
> On Nov 13, 2020, at 10:58, Larry Dalton wrote:
>
> Error code “Project ** raised exception class ‘EReadError with unknown
> property ‘AutoCommit’
>
Error code “Project ** raised exception class ‘EReadError with unknown
property ‘AutoCommit’
Sent from my iPhone
--
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus
13 matches
Mail list logo
