> On Dec 21, 2023, at 12:06 PM, Hairy Pixels wrote:
>
> Here's another example of this. If I use an array Finalize is called 4 times
> but Initialize is never called, unless you assign a record to the array and
> then it's called once.
>
> This makes even less sense. What's the idea behind
On 12/21/23 07:06, Hairy Pixels via fpc-pascal wrote:
On Dec 21, 2023, at 6:11 AM, Hairy Pixels wrote:
Maybe I misunderstood but I thought they were supposed to be balanced with init
calls. Is it the design of the compiler to allow multiple finalize calls and
have the user keep track of it
On 12/21/23 01:11, Hairy Pixels via fpc-pascal wrote:
On Dec 21, 2023, at 1:53 AM, Michael Van Canneyt via fpc-pascal
wrote:
If you look at the generated code, you see that there is an implicit
try/finally block
and the finally block does a finalize.
Maybe I misunderstood but I thought t
> On Dec 21, 2023, at 6:11 AM, Hairy Pixels wrote:
>
> Maybe I misunderstood but I thought they were supposed to be balanced with
> init calls. Is it the design of the compiler to allow multiple finalize calls
> and have the user keep track of it the underlying structure is really
> finalize
> On Dec 21, 2023, at 1:53 AM, Michael Van Canneyt via fpc-pascal
> wrote:
>
> If you look at the generated code, you see that there is an implicit
> try/finally block
> and the finally block does a finalize.
Maybe I misunderstood but I thought they were supposed to be balanced with init
c
On Wed, 20 Dec 2023, Hairy Pixels via fpc-pascal wrote:
I feel like this was addressed but I couldn't find any references. The program
below prints the following:
Initialize
Create
Finalize
Finalize
Why is Finalize called twice? I thought those were supposed to be called in
pairs with
I feel like this was addressed but I couldn't find any references. The program
below prints the following:
Initialize
Create
Finalize
Finalize
Why is Finalize called twice? I thought those were supposed to be called in
pairs with initialize?
==
{$mode objfpc}
{$modeswi
