(Enter summary)
Abstract: We present a detailed analysis of the possible ways in which the execution of an
Ada 95 program might become "totally unpredictable". In particular, we discuss
those language aspects which allow a program execution to become erroneous or
which have an undefined semantics. The Ada 95 language definition is assessed
with respect to its completeness and clarity in presenting these aspects. The
evolution of these aspects from Ada 83 to Ada 95 is summarised.
Categories and Subject Descriptors: ... (Update)
Active bibliography (related documents): More All
0.0: Commands as Media: Design and Implementation of a Command.. - Herlocker, Konstan (1995)
(Correct)
0.0: An Investigation into The Application of Active Networks to Mobile .. - Chin (2000)
(Correct)
0.0: JaDE: Access Control in a Java-Based Object Database - Jones Winslett (1995)
(Correct)
Similar documents based on text: More All
0.4: Coding Regulations for Safety Critical Software Development - Mazzanti
(Correct)
0.1: Representation and Visualization of Terrain Surfaces at.. - Cignoni, Puppo, Scopigno (1997)
(Correct)
0.1: Formalising Engineering Judgement on Software.. - Delic, Mazzanti.. (1997)
(Correct)
BibTeX entry: (Update)
@misc{ mazzanti-guide,
author = "Franco Mazzanti",
title = "Guide to Erroneous Executions in Ada 95 (how [not] to shoot yourself in
the foot)",
url = "citeseer.ist.psu.edu/mazzanti97guide.html" }
Citations (may not include all citations):
29
The Java Language: A White Paper (context) - Microsystems
Documents on the same site (http://rep1.iei.pi.cnr.it/people/mazzanti/pub.html):
A Symbolic Model Checker for ACTL - Fantechi, Gnesi, Mazzanti.. (1998)
(Correct)
Formalising Engineering Judgement on Software.. - Delic, Mazzanti.. (1997)
(Correct)
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC