unit init, finalize and init_implicit, finalize_implicit.

[JernejL]

Adding to this thread:
 
See attachment.
 
If finalize_implicit is only called when unit is "finalized" - implying that program has to terminate, why do i see these TDC_GAME_$$_finalize_implicit$ calls in profiling (application was not terminated to call any unit finalization)?
 
Additionally, TDC_GAME unit does not even have a initialization or finalization section at all.. why is TDC_GAME_$$_finalize_implicit$ then even in debug symbols, and why does it show up in profiling as being called? 
 

[Zvoni]

Additionally, TDC_GAME unit does not even have a initialization or finalization section at all.. why is TDC_GAME_$$_finalize_implicit$ then even in debug symbols, and why does it show up in profiling as being called?

As Thaddy wrote: Does the TDC_GAME-Unit depend on a unit which HAS explicit Finalization?
Or as PascalDragon wrote: Does this TDC_Game-unit has a, for example, Typed AnsiString-Constant?

[JernejL]

I try to avoid ansistring as much as possible, and nearly all strings in my code are unicodestrings, with some widestrings where winapi is needed.
 
Still, that does not explain why finalization would even be called when program was never terminated.
 

[Zvoni]

I try to avoid ansistring as much as possible, and nearly all strings in my code are unicodestrings, with some widestrings where winapi is needed.
 
Still, that does not explain why finalization would even be called when program was never terminated.

Ansistring was just an example.
PascalDragon probably meant: any managed type.

And finalization has nothing to do with if your program terminates.

It probably has more to do, if a used managed Type goes out of scope.

As far as i understood it:
Unit1 uses Unit 2
Unit 2 uses Unit 3, which PROVIDES a managed type (e.g. UnicodeString).
Unit 2 does its calculations USING the type from Unit 3.
Unit 2 finishes its calculations and returns control back to Unit 1.
In that case Unit 2 would get an implicit finalization

At least that's how i understand it

[Thaddy]

Considering Ansi vs Unicode strings does not have any effect: BOTH are managed string types.
@Zvoni
posts crossed.

[Zvoni]

Considering Ansi vs Unicode strings does not have any effect: BOTH are managed string types.
@Zvoni
posts crossed.

Well, as long as we "don't cross the streams" we should be fine....

[PascalDragon]

If finalize_implicit is only called when unit is "finalized" - implying that program has to terminate, why do i see these TDC_GAME_$$_finalize_implicit$ calls in profiling (application was not terminated to call any unit finalization)?

It might be that this is a false positive as whatever you use for profiling might associate that symbol name with some other function. Can you take a look at the generated assembly code of the unit (option -al) and what is placed around the TDC_GAME_$$_finalize_implicit$?
 

Additionally, TDC_GAME unit does not even have a initialization or finalization section at all.. why is TDC_GAME_$$_finalize_implicit$ then even in debug symbols, and why does it show up in profiling as being called?

That's the point of the implicit finalization, it's for global variables that need to be finalized, not the finalization-section.