HIL~STD-1589C (USAF) e (This document has been approved! 6 July 1964 { for public release and sale: its supensepire——— |_distribution 1s unlimited t MIL-STD-1589B (USAF) a 6 June 1980 MILATARY STANDARD ¢e JOVIAL (J73) “We deliverable data is required; by this document. 5 FSC IPSCMIL-STD-1589C (USAF) 6 July 1984 DEPARTMENT OF AIR FORCE Washington DC 20301 JOVIAL (J73) MIL-STD-1589¢ 1, This Military Standard is approved for use by the Department of the Air Force, and is available for use by all Departments and Agencies of the Department of Defense. 2. Recommendations, corrections, additions, or deletions should be addressed to: Conmander, Rome Air Development Center, Attn: RBE-2, Griffiss APB NY 13441. ihMIL-STD-1589¢ (USAF) 6 July 1984 FOREWORD This Tevised document was coordinated as Change Notice 1 to HIL-STD-15898. Due to the extent of changes it has been approved as MIL-SID-1589C.. This Version contains no changes fro the coordinated version other than those required for reformatting. MIL-STD-1589C (USAF) defines the upgraded JOVIAL (J73) programming language. The sections are organized in a top-down manner. The first section describes the interactions between the modules of the complete program so that in subsequent sections the structures of the language can be described (to the extent possible) without reference to their interaction with other structures, Most sections are divided into separate parts entitled “syntax,” {Semantics," and "Constraints." The "Syntax" descriptions define the grammar of the language in a modified BNF notation. The "Semantics" discussions define the geaning of constructs that satisfy the Syntax and Constraints. the {Sonstraints" discussions enumerate non-syntactic requirements that must be met jn order for the given constructs to be legal. The intent is that. the Syntax, Semantics, and Constraints not be redundant with each other ~ e.g., the Semantics sections do not normally repeat something that should de obvious from the Syntax, neither do they repeat stipulations that are listed as Constraints, Some of the designated Constraints apply at compile tine, and others pertain to errors that are not detectable until the compiled program is executes. In order to conform to this standard, a J73 compiler must detect compile-tine errors, but it is not required to generate code for run-time checks. The Appendix provides a cross-reference index to constructs that appear in the Syntax. For each construct, the index gives the number of the section where that ‘construct is defined and the numbers of the sections where that construct is used in a definition. The following metalanguage conventions have been observed in this docunent: ‘+ Terminal symbols, i.e., those which actually appear in a program are written in upper case. for example: BEGIN END STATIC 2. Non-terminal symbols, i.e., those which represent groups of terminal symbols are written in lower case and enclosed between < and >. If any non-terminal symbol is longer than one word, the words are separated by a hyphen. For example: iit