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=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ncar!tank!nucsrl!gore
From: gore@eecs.nwu.edu (Jacob Gore)
Newsgroups: comp.lang.ada
Subject: Re: Vendor introduces "safe" Ada subset
Message-ID: <3930021@eecs.nwu.edu>
Date: 15 Oct 88 18:43:36 GMT
References: <6073@june.cs.washington.edu>
Organization: Northwestern U, Evanston IL, USA
List-Id: <comp.lang.ada>

/ comp.lang.ada / jon@june.cs.washington.edu (Jon Jacky) / Oct 14, 1988 /
>... To achieve Ada integrity, Spark has introduced several restrictions.  It
>does not allow the use of tasks, exceptions or generic units.  Access types 
>are also omitted, as these are considered unacceptable in real-time safety
>critical applications.  ... Certain features - such as "go to" statements
>and "declare" statements - are totally barred.

Interesting.  Removing EXCEPTIONS to achieve safe programming?

Sounds like what's left is Modula-2 with overloading (or is that "barred"
also?).

Jacob Gore				Gore@EECS.NWU.Edu
Northwestern Univ., EECS Dept.		{oddjob,gargoyle,att}!nucsrl!gore