[ HPF Home | Versions | Compilers | Projects | Publications | Applications | Benchmarks | Events | Contact ]

Next: HPF-Conforming and Subset-Conforming Up: Overview Previous: Fortran 90 and

Notation

This document uses the same notation as the Fortran~90 standard. In particular, the same conventions are used for syntax rules. BNF descriptions of language features are given in the style used in the Fortran~90 standard. To distinguish HPF syntax rules from Fortran~90 rules, each HPF rule has an identifying number of the form Hsnn, where s is a one-digit major section number and nn is a one- or two-digit sequence number. The syntax rules are also collected in Annex . Nonterminals not defined in this document are defined in the Fortran 90 standard. Also note that certain technical terms such as ``storage unit'' are defined by the Fortran 90 standard; Annex identifies the Fortran 90 rules defining these nonterminals. References in parentheses in the text refer to the Fortran 90 standard.

[]Rationale. Throughout this document, material explaining the rationale for including features, choosing particular feature definitions, and other decisions is set off in this format. Readers interested in the language definition only may wish to skip these sections, while readers interested in language design may want to read them more carefully. (End of rationale.)

[]Advice to users. Throughout this document, material that is primarily commentary for users (including most examples of syntax and interpretation) is set off in this format. Readers interested in technical material only may wish to skip these sections, while readers wanting a more basic approach may want to read them more carefully. (End of advice to users.)

[]Advice to implementors. Throughout this document, material that is primarily commentary for implementors is set off in this format. Readers interested in the language definition only may wish to skip these sections, while readers interested in compiler implementation may want to read them more carefully. (End of advice to implementors.)

©2000-2006 Rice University

[ Contact Us | HiPerSoft | Computer Science ]

paula@erc.msstate.edu
Thu Dec 8 16:17:11 CST 1994