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.1 required=5.0 tests=BAYES_40,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!COMMUNITY-CHEST.MITRE.ORG!howell
From: howell@COMMUNITY-CHEST.MITRE.ORG (Chuck Howell)
Newsgroups: comp.lang.ada
Subject: Validation policies and procedures for AJPO
Message-ID: <9005241500.AA00129@community-chest.mitre.org>
Date: 24 May 90 15:00:34 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
List-Id: <comp.lang.ada>

I went to scarf up a copy of "val-proc.hlp" from ajpo.sei.cmu.edu
(described as "text of the AJPO validation procedures and guidelines
issued on 1 Jan 1987), but it bears remarkable similarity to a certain
famous Fuzzy Wuzzy: it wasn't there!

Anyone have recent scoop on explicit AJPO policy statements re
validation?  I'm specifically interested in how constraining they are
about how far one can go with extensions/modification to a compiler or
ARTE before you need to revalidate.

Thanks,
    Chuck


+------------------------------------------------------------------------+
| Chuck Howell, M/S Z645     INTERNET: howell@community-chest.mitre.org  |
| The MITRE Corporation           OR   howell@mwunix.mitre.org           |
| 7525 Colshire Drive           VOICE: (703) 883-6080                    |
| McLean VA 22102-3481            FAX: (703) 883-5519                    |
+------------------------------------------------------------------------+