Re: Question about library-level functions

[AdaMagica <christ-usch.grein@t-online.de>]

> As a result, lifetime.Finalize was called twice.
> % ./main
> before
> Initialize (0000000100100090)
> Finalize (0000000100100090)
> lifetime
> Finalize (0000000100100090)
> after

 Hm, I'm no lnaguage lawer, but this looks wrong to me.

> > Finalize may not be called in Alloc,  
> Surely, lifetime.Finalize may be called in 'Alloc'.
>
> The backtrace of gdb is:
>
> #0  lifetime__finalize__2 (object=) at lifetime.adb:7
> #1  0x0000000100001a9c in lifetime__tFD () at lifetime.adb:4
> #2  0x000000010000da39 in system__finalization_masters__finalize (master=) at s-finmas.adb:241
> #3  0x00000001000026d8 in _ada_alloc () at alloc.adb:5
> #4  0x00000001000028f2 in _ada_main () at main.adb:11

Don't know what's happening here...

> > since the object must be created in place
> > (it's limited - there cannot be an intermediate object as in the unlimited 
> > case). 
>
> lifetime.T is limited. However, an access value of it is not limited.

Irrelevant, since it's an object of type T that's finalized here at the end of the lifetime of the corresponding access type.

> Perhaps AARM 7.6.1 says the anonymous access type belongs to innermost master.
> The master is usually in the package and lets objects live long time.
> I imagine, if a function is library-level, there is no place which it
> puts the master, so the master is inside of the function...???

Hm, the master of type A is the access block.

But I'm not sure who the master is of the anonymous access type declared with function Alloc. It should be the environment task, just as that is ultimately the master of any library unit (be it a package or a subprogram).

In effect, I do not really understand what is happening here...