TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mime-Version:
1.0
Sender:
"Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
X-To:
Samuel Mize <[log in to unmask]>
Date:
Wed, 5 Nov 1997 14:55:18 -0500
Reply-To:
"Robert I. Eachus" <[log in to unmask]>
Subject:
From:
"Robert I. Eachus" <[log in to unmask]>
In-Reply-To:
Content-Type:
text/plain; charset="us-ascii"
Parts/Attachments:
text/plain (25 lines)
At 09:50 AM 11/5/97 -0600, Samuel Mize wrote:

>MY MISTAKE!  The default policy is undefined.  an Annex-D-compliant
>implementation LETS YOU SPECIFY this policy.

   There is an even more important statement you can make, which the powers
that be are tying to make true:

   "If your validated compiler accepts the pragma, you will get the
required behavior."

   In other words, it is not correct for an implementation to ignore this
or any other annex defined pragma.  The only RM compliant behavior is to
either reject the pragma or to implement the Annex defined behavior--and
not a subset of it--whether or not the Annex is officially supported.

  I'm not sure if an AI on this will be forthcoming, but I expect it to be
a confirmation not a ramification.

                                        Robert I. Eachus

with Standard_Disclaimer;
use  Standard_Disclaimer;
function Message (Text: in Clever_Ideas) return Better_Ideas is...

ATOM RSS1 RSS2