Re: Problem with Delay Alternative in Finalization

[Tim McGuire <mcguire_tm2@yahoo.com>]

On Sat, 19 May 2012 20:46:25 +0100, Robert Matthews
<ignore@ramatthews.free-online.co.uk> wrote:

>Dmitry A. Kazakov wrote:
>
>> On Fri, 18 May 2012 21:30:31 -0500, Tim McGuire wrote:
>> 
>>> I am running in to a problem where a delay alternive used when in
>>> finalization doesn't seem to be working properly.
>>> The delay part never seems to happen.
>> 
>> It is Program_Error to propagate an exception from Initialize, which is
>> what I think happens when you raise Lock_Timeout_Exception.
>> 
>> BTW, you can use task identification in order to allow reentrant locks.
>> 
>
>In the 2005 standard at 7.6.1 para 14.a: "It is not a bounded error for 
>Initialize to propagate an exception. If Initialize propagates an exception, 
>then no further calls on Initialize are performed, and those components that 
>have already been initialized (either explicitly or by default) are 
>finalized in the usual way."
>
>So Program Error is not raised from Initialize - though
>on general grounds it may well be best to avoid raising exceptions in
>an Initialize.
>
>Robert

I agree that raising exceptions in an Initialize isn't the best way to
do things.

However, this is the way the application was written for Solaris and I
am just porting it to Red Hat Linux.

The fact still remains that it appears that the Delay alternative is
not working properly in initialize, when compiled with GCC4.3.4.

Is there some way to fix this? Compiler switch, pragma, or maybe
upgrading compiler (i.e. newer version of GCC or GNATPRO)?





Tim