From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: Protected handlers & entry bodies
Date: Tue, 20 Jan 2015 22:46:24 +0000
Organization: A noiseless patient Spider
Message-ID: <lyh9vlnk8v.fsf@pushface.org>
References: <lyy4ozof2x.fsf@pushface.org> <m9joq8$8ga$1@loke.gir.dk>
	<lytwzmo3kp.fsf@pushface.org> <m9mjfl$94q$1@loke.gir.dk>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mx02.eternal-september.org;
 posting-host="8878eaae66d49f7d529ec3c7abf78fb7";
	logging-data="27661"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1/c+mfpZPkcC7NE8a3B0m/tycL4m5GqgUo="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (darwin)
Cancel-Lock: sha1:4DImBXNmVoM/bPJsO4ZaOfMR+iU=
	sha1:thuXqA1ceeXf1QKlG7FFpc9Pi6E=
Xref: news.eternal-september.org comp.lang.ada:24653
Date: 2015-01-20T22:46:24+00:00
List-Id: <comp.lang.ada>

"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!