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_50,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!pyrnj!mirror!gabriel!ada-uts!stt
From: stt@ada-uts
Newsgroups: comp.lang.ada
Subject: Re: compiler validation
Message-ID: <4700084@ada-uts>
Date: Thu, 6-Nov-86 10:52:00 EST
Article-I.D.: ada-uts.4700084
Posted: Thu Nov  6 10:52:00 1986
Date-Received: Mon, 10-Nov-86 22:05:53 EST
References: <1029@ucbvax.berkeley.edu>
Nf-ID: #R:ucbvax.berkeley.edu:-102900:ada-uts:4700084:000:755
Nf-From: ada-uts!stt    Nov  6 10:52:00 1986
List-Id: <comp.lang.ada>


Ada compilers must be revalidated periodically (it used to be
every year; now it is every two years).  This is because the
validation suite becomes more stringent as time goes on,
and the language review board "refines" the official
interpretation of the language reference manual.  This
is not directly due to the size of the compilers (though they
are admittedly big), but rather both are due to the
size of the language and the extraordinary concern for precision
in the language definition.

Yes, there is an implementor's guide (available on the ArpaNet
somewhere), but it is not exactly a compiler-writer's cookbook.
Rather it is a series of tips about what to watch out for,
as well as motivation and explanation for parts of the validation
suite.