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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,5a05d88755a62a0e X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: Asynchronous Transfer of Control Date: 1996/10/23 Message-ID: #1/1 X-Deja-AN: 191628629 references: <32656457.1A76@csehp1.mdc.com> <326E3BD9.62CB@csehp1.mdc.com> organization: New York University newsgroups: comp.lang.ada Date: 1996-10-23T00:00:00+00:00 List-Id: James Squire says "They have not released their implementation of Annex D yet. I will forward this on to them. I think it would have been clearer to place your sentence into the LRM to let people know that abort completion points are only important if the compiler does not support preemptive abort." The RM is quite clear, in 9.8, we have 24 (40) Additional requirements associated with abort are given in D.6, ``Preemptive Abort''. And in the referenced section D.6, we find D.6 Preemptive Abort 1 This clause specifies requirements on the immediacy with which an aborted construct is completed. I don't know where else you would look int the RM for semantics of abort other than these two sections. Note that it is NOT the case that abort completion points are only important if the compiler does not support preemptive abort, I don't know where you got this idea. The rule is that an abort CANNOT happen later than the point of an abort completion point, and this absolute rule applies regardless of the requirements in D.5(2-12) which do NOT contains this specific requirement.