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!jarvis.csri.toronto.edu!cs.utexas.edu!usc!brutus.cs.uiuc.edu!uakari.primate.wisc.edu!ames!pasteur!ucbvax!CTC.CONTEL.COM!mathis
From: mathis@CTC.CONTEL.COM (Bob Mathis  x4232)
Newsgroups: comp.lang.ada
Subject: 10 Commandments for Ada9X
Message-ID: <9002021545.AA03784@ctc.contel.com>
Date: 2 Feb 90 15:45:21 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
List-Id: <comp.lang.ada>

This message contains some ideas for a "Ten Commandments" for the
requirements and revision of Ada. I have brought together some
ideas that I think are related and given them titles. If this
list doesn't provoke some discussion, then some net nodes must be
inoperative.

1. PUBLIC -- involve public in all phases of revision and
standardization; be responsive to various special interest
communities; continue focus on primary customers; coordinate with
Ada-related professional groups

2. CONSERVATIVE -- minimum change with maximum positive impact;
maximum compatibility with current programs and compilers;
generally conservative; revision not redesign

3. ISO -- revision of text to incorporate approved AIs; use of
large character set in strings and literals; adapt for better fit
with other ISO standards and guidelines

4. OOP -- increased support for object-oriented program
development paradigm while remaining consistent with Ada's
support for other paradigms and Ada's existing features
addressing similar goals

5. REAL-TIME -- improved suitability for and predictability of
real-time performance (dynamic priorities, distributed time-outs,
aborts, asynchronous communication, etc.); require more
documentation of run-time performance in Appendix F

6. RELIABLE -- features for improving reliability of applications
programs; maximize the possibilities for static analysis of
program correctness

7. INTERFACES -- improved facilities for interfacing to external
systems (GKS, CCIS, X, SQL, etc.); secondary and supplemental
standards for use with commercial data processing; adaptation to
multi-lingual environments

8. SIMPLIFY/UNIFY -- improve overall language consistency; remove
unnecessary limits and "silly" requirements in the current
language; reduce implementation freedom/inconsistency (clarify
and specify in RM); increase language orthogonality; increase
language integration; improve the similarity between user defined
and predefined constructs (types, exceptions, etc.); improve Ada
from the perspective of "least surprise"

9. STRICT CONFORMANCE -- continued strict enforcement of no
subsets/no supersets; but encourage compiler writers and tool
developers to experiment with new ideas for supporting program
development

10. KEEP IT ADA -- keep strong typing, encapsulation, separate
compilation, information hiding, static binding, packages, tasks,
rendezvous, generics, and other aspects of current Ada approach