From: "Randy Brukardt" <randy@rrsoftware.com>
Subject: Re: Protected handlers & entry bodies
Date: Wed, 21 Jan 2015 14:39:33 -0600
Date: 2015-01-21T14:39:33-06:00 [thread overview]
Message-ID: <m9p2q5$426$1@loke.gir.dk> (raw)
In-Reply-To: lyh9vlnk8v.fsf@pushface.org
"Simon Wright" <simon@pushface.org> wrote in message
news:lyh9vlnk8v.fsf@pushface.org...
> "Randy Brukardt" <randy@rrsoftware.com> writes:
>
>> I see. Your point is that GNAT is buggy and that's likely to cause
>> problems
>> in some obscure and non-reproducible cases.
>>
>> But this has nothing to do with the language. Just because there is a
>> permission to do something (use some other task to execute an entry body)
>> does not mean that it should be used, especially if that is potentially
>> causing problems.
>
> Not sure that GNAT's actually buggy. Re-reading C.3.1(17):
>
> When the aspects Attach_Handler or Interrupt_Handler are specified
> for a protected procedure, the implementation is allowed to impose
> implementation-defined restrictions on the corresponding
> protected_type_declaration and protected_body.
>
> it seems to me it'd be fair to claim that restrictions could be imposed
> on entry bodies. With my current implementation, one such would be to
> disallow the use of Ada.Real_Time.Clock!
Good point. I read that too quickly and confused protected_body with
subprogram_body.
Randy.
prev parent reply other threads:[~2015-01-21 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 23:15 Protected handlers & entry bodies Simon Wright
2015-01-19 20:18 ` Randy Brukardt
2015-01-19 21:36 ` Simon Wright
2015-01-20 22:05 ` Randy Brukardt
2015-01-20 22:46 ` Simon Wright
2015-01-21 20:39 ` Randy Brukardt [this message]
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox