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.6 required=5.0 tests=BAYES_05,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!husc6!think!ames!ucbcad!ucbvax!cf4.UCI.EDU!cha
From: cha@cf4.UCI.EDU (Sung Deok Cha)
Newsgroups: comp.lang.ada
Subject: Fault-Prone Ada features wanted
Message-ID: <8705131629.aa03667@ROME.UCI.EDU>
Date: Wed, 13-May-87 21:51:52 EDT
Article-I.D.: ROME.8705131629.aa03667
Posted: Wed May 13 21:51:52 1987
Date-Received: Sat, 16-May-87 07:23:04 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
List-Id: <comp.lang.ada>

We are making up a list of features of the Ada language which may be
prone to faults when they are used.  For example, an abort may
interrupt a task while it is updating a global variable; this may
contribute to a particular failure of a program.  We are only
considering features of the language as described in the Language
Reference Manual, and we are assuming that the language implementation
provides all of the functionality guaranteed by the LRM.  We would
appreciate it if people would point out features of Ada which they have
found to be fault-prone, or which have caused them problems in the
past.  Examples (program listing or discussion) would also be welcome.
Please send responses to this message directly to me; if there is
sufficient interest, I will post a summary to the list.
					S. D. Cha
ARPA: cha@ics.uci.edu
UUCP: ucbvax!ucivax!cha
BITNET:cha%ics@ucicp6.BITNET
USMail: S. D. Cha, ICS Department, University of California, Irvine,
        Irvine, CA 92717