Ada 83

Ada 83

(language)
The original Ada, as opposed to Ada 95.
References in periodicals archive ?
Enhancements include support for floating point overflow on unconstrained types, the ability to supply target configuration files and improved support for existing codebases in Ada 83. The latest update to CodePeer features more precise diagnostic messages and fewer "false positives"' an independent Ada front end making it even more efficient and flexible; and better integration with AdaCore's two IDEs: GNAT Programminng studio (GPS) and GNATbench (the GNAT Pro Ada plug-in for Eclipse and Wind River Systems Workbench).
"Out of the box," ACS and OCS support C, C++, Java, and optionally Ada 83, Ada 95 and SPARK.
The Rockwell Collins cockpit management system in the MH-47D, MH-60L, and MH-6/AH-6 uses ADA 83. Fleet upgrades must be written in both languages, and the proprietary architectures require costly regression testing when functions are changed or capabilities are added.
Ada 83 supplied a fixed-point arithmetic facility that was a close semantic match for the requirements of exact decimal computation.
In addition, Ada 9X generalizes the Ada 83 concept of access types (pointer types) to allow them to point to statically allocated objects, as well as to subprograms.
Ada 83 has been called an "object-based" language [3, 9], but it does not qualify as a true "object-oriented" language because it lacks full support for inheritance and run-time polymorphism [6].
Ada 83 has a rich abstract data type (ADT) definition capability.
For example, in Ada 83 a new type may be defined in terms of an existing type as follows: type Fancy[underscore]Window is new
Mature Ada 9X compilers must become available in much less time than it took to produce Ada 83 compilers.
A distinction needs to be made between the complexity perceived by an Ada novice and that seen by a user transitioning from Ada 83. For the latter, practically any change will, for some time, mean complexity, since a relearning process needs to occur.
In Ada 83, this conflict was partially addressed by leaving certain semantics implementation-defined.
The difficult challenge to the Ada 9X teams and the standardization bodies is to arrive at such a compromise, making Ada 9X acceptable and attractive as a progression of Ada 83 for all user communities.