ISO IEC 14977-1996 Information technology - Syntactic metalanguage - Extended BNF《信息技术 语法元语言 扩展的BNF》.pdf

《ISO IEC 14977-1996 Information technology - Syntactic metalanguage - Extended BNF《信息技术 语法元语言 扩展的BNF》.pdf》由会员分享，可在线阅读，更多相关《ISO IEC 14977-1996 Information technology - Syntactic metalanguage - Extended BNF《信息技术 语法元语言 扩展的BNF》.pdf（21页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL STANDARD ISO/IEC First edition 1996-I 2-l 5 Information technology - Syntactic metalanguage - Extended BNF Technologies de /information - MBtalangage syntaxique - BNF Btendu Reference number ISO/IEC 14977:1996(E) ISO/IEC 14977 : 1996(E) Contents Page Foreword . . . . . . . . . . . . .

2、. . . . . . . . . . . . . . . . . . , . . . . . . . . . . . iv Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Scope 2 Normative references 3 Definitions 4 The form of each syntactic element of Extended BNF 4.1 General . 4.2 Syntax . 4.3 Syntax-rule 4.4 Definitions-list.

3、 . 4.5 Single-definition . 4.6 Syntactic-term 4.7 Syntactic exception 4.8 Syntactic-factor . 4.9 Integer . 4.10 Syntactic-primary 4.11 Optional-sequence . 4.12 Repeated sequence . 4.13 Grouped sequence . 4.14 Meta-identifier 4.15 Meta-identifier-character . 4.16 Terminal-string. . 4.17 First-termina

4、l-character 4.18 Second-terminal-character 4.19 Special-sequence 4.20 Special-sequence-character . 4.21 Empty-sequence . 4.22 Further examples V 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3 3 3 3 3 ISO/IEC 1996 All rights reserved. Unless otherwise specified, no pan of this publication may be reprodu

5、ced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the publisher. ISO/IEC Copyright Office l Case Postale 56 l CH-1211 Gerkve 20 l Switzerland Printed in Switzerland ii ISO/IEC ISO/IEC 14977 : 1996(E) 5 The

6、symbols represented by each syntactic element. . 5.1 General . 5.2 Terminal-string. . 5.3 Meta-identifier 5.4 Grouped-sequence . 5.5 Optional-sequence . 5.6 Repeated-sequence . 5.7 Syntactic-factor . 5.8 Syntactic-term 5.9 Single-definition . 5.10 Definitions-list 5.11 Special-sequence 5.12 Empty-se

7、quence . 6 Layout and Comments . 6.1 General . 6.2 Terminal-character . 6.3 Gap-free-symbol 6.4 Gap-separator 6.5 Commentless-symbol . 6.6 Comment-symbol 6.7 Bracketed-textual-comment . 7 The representation of each terminal-character in Extended BNF 7.1 General . 7.2 Letters and digits 7.3 Other ter

8、minal characters 7.4 Alternative representations. . 7.5 Other-character . 7.6 Gap-separator 7.7 Terminal-characters represented by a pair of characters . 7.8 Invalid character sequences . 8 Examples . 8.1 The syntax of Extended BNF . 8.2 Extended BNF used to define itself informally . 8.3 Extended B

9、NF defined informally Annexes A Two-level grammars . B Bibliography 3 3 4 4 4 4 4 4 4 5 5 5 5 8 8 10 IO I1 12 . . . 111 ISO/IEC 14977 : 1996(E) ISO/IEC Foreword IS0 (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized syste

10、m for worldwide standardization. National bodies that are members of IS0 or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. IS0 and IEC technical committees col

11、laborate in fields of mutual interest. Other international organizations, governmental and non- governmental, in liaison with IS0 and IEC, also take part in the work. In the field of information technology, IS0 and IEC have established a joint technical committee ISO/IEC JTC 1. Draft International S

12、tandards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75% of the national bodies casting a vote. International Standard ISO/IEC 14977 was prepared by BSI (as BS 6154) and was adopted, und

13、er a special “fast-track procedure”, by Joint Technical Committee ISO/IEC JTC 1, Znfomtation technology, in parallel with its approval by national bodies of IS0 and IEC. Annexes A and B of this International Standard are for information only. iv ISO/IEC ISO/IEC 14977 : 1996(E) Introduction A syntact

14、ic metalanguage is an important tool of computer science. The concepts are well known, but many slightly different notations are in use. As a result syntactic metalanguages are still not widely used and understood, and the advantages of rigorous notations are unappreciated by many people. Extended B

15、NF brings some order to the formal definition of a syntax and will be useful not just for the definition of programming languages, but for many other formal definitions. Since the definition of the programming language Algol 60 (Naur, 1960) the custom has been to define the syntax of a programming l

16、anguage formally. Algol 60 was defined with a notation now known as BNF or Backus-Naur Form. This notation has proved a suitable basis for subsequent languages but has frequently been extended or slightly altered. The many different notations are confusing and have prevented the advantages of formal

17、 unambiguous definitions from being widely appreciated. The syntactic metalanguage Extended BNF described in this standard is based on Backus-Naur Form and includes the most widely adopted extensions. Syntactic metalanguages A syntactic metalanguage is a notation for defining the syntax of a languag

18、e by use of a number of rules. Each rule names part of the language (called a non-terminal symbol of the language) and then defines its possible forms. A terminal symbol of the language is an atom that cannot be split into smaller components of the language. A syntactic metalanguage is useful whenev

19、er a clear formal description and definition is required, e.g. the format for references in papers submitted to a journal, or the instructions for performing a complicated task. A formal syntax definition has three distinct uses: a) it names the various syntactic parts (i.e. non-terminal symbols) of

20、 the language; b) it shows which sequences of symbols are valid sentences of the language; c) it shows the syntactic structure of any sentence of the language. The need for a standard syntactic metalanguage Without a standard syntactic metalanguage every programming language definition starts by spe

21、cifying the metalanguage used to define its syntax. This causes various problems: V ISO/IEC 14977 : 1996(E) ISO/IEC Many different notations - It is unusual for two different programming languages to use the same metalanguage. Thus human readers are handicapped by having to learn a new metalanguage

22、before they can study a new language. Concepts not widely understood - The lack of a standard notation hinders the use of rigorous unambiguous definitions. Imperfect notations - Because a metalanguage needs to be defined for every programming language, almost inevitably, the metalanguage contains de

23、fects. For example errors occurred in the drafting of RTLJ2 (BS5904) and CORAL 66 (BS5905) because the metalanguages could not be typed easily. Special purpose notations - A metalanguage defined for a particular pro- gramming language is often simplified by taking advantage of special features in th

24、e language to be defined. However, the metalanguage is then unsuitable for other programming languages. Few general syntax processors - The multiplicity of syntactic meta- languages has limited the availability of computer programs to analyse and process syntaxes, e.g. to list a syntax neatly, to ma

25、ke an index of the symbols used in the syntax, to produce a syntax-checker for programs written in the language. In practice experienced readers have little difficulty in picking up and learning a new notation, but even so the differences obscure mutual understanding and hinder communication. A stan

26、dard metalanguage enables more people to crystallize vague ideas into an unambiguous definition. It is also useful because other people needing to provide formal definitions no longer need to reinvent similar concepts. The objectives to be satisfied It is desirable that a standard syntactic metalang

27、uage should be: a) concise, so that languages can be defined briefly and thus be more easily understood; b) precise, so that the rules are unambiguous; c) formal, so that the rules can be parsed, or otherwise processed, by a computer when required; d) natural, so that the notation and format are rel

28、atively simple to learn and understand, even for those who are not themselves language designers; (The meaning of a symbol should not be surprising. It should also be possible to define the syntax of a language in a way that helps to indicate the meaning of the constructions.) e) general, so that th

29、e notation is suitable for many purposes including the description of many different languages; f) simple in its character set and with a notation that avoids, as far as is practicable, using characters that are not generally available on standard keyboards (both typewriters and computer terminals)

30、so that the rules can be typed and can be processed by computer programs; g) self describing, so that the notation is able to describe itself; vi ISO/IEC ISO/IEC 14977 : 1996(E) h) linear, so that the syntax can be expressed as a single stream of characters. (This simplifies printing a syntax. Compu

31、ter processing of a syntax is also simpler.) Some common syntactic metalanguages Unfortunately none of the existing syntactic metalanguages was suitable for adoption as the standard, for example: a) COBOL (IS0 1989:1985) lists alternatives vertically and uses brackets spreading over many lines. This

32、 is inconvenient for computer processing and cannot be prepared on typewriters. b) Backus-Naur Form (used in ALGOL 60) has problems if the metasymbols 1 := occur in the language being defined. Some common forms of construction (e.g. comments) cannot be expressed naturally, other constructions (e.g.

33、repetition) are long-winded. c) The obsolete FORTRAN 77 (IS0 1539:1980) had railroad tracks. These are easy to understand but difficult to prepare and to process on a computer or typewriter. The current version, FORTRAN 90 (ISO/IEC 1539:1991), no longer uses this notation. Most other languages use a

34、 variant of one of these metalanguages. Most of them cannot be candidates for standardization because they use characters not in the language being defined as metasymbols of the metalanguage. This simplifies the metalanguage but prevents it from being used generally. POSIX (ISO/IEC 9945-2: 1993) inc

35、ludes two complementary facilities which both assume an ISO/IEC 646:1991 character set is applicable: LEX permits the definition and lexical analysis of regular expressions, but is inadequate for the description of an arbitrary context-free grammar, and YACC (Yet Another Compiler Compiler) is a pars

36、er generator for an LALR(l) grammar. The standard metalanguage Extended BNF Extended BNF, the metalanguage defined in this International Standard, is based on a suggestion by Niklaus Wirth (Wirth, 1977) that is based on Backus-Naur Form and that contains the most common extensions, i.e.: a) Terminal

37、 symbols of the language are quoted so that any character, including one used in Extended BNF, can be defined as a terminal symbol of the language being defined. b) 1 and 1 indicate optional symbols. c) and indicate repetition. d) Each rule has an explicit final character so that there is never any

38、ambiguity about where a rule ends. e) Brackets group items together. It is an obvious convenience to use ( and ) in their ordinary mathematical sense. The main differences in Extended BNF are further features that experience has shown are often required when providing a formal definition: vii ISO/IE

39、C 14977 : 1996(E) ISO/IEC a) Dejining an explicit number of items. Fortran contains a rule that a label field contains exactly five characters; an identifier in PUI or COBOL has up to 32 characters: rules such as these can be expressed only with difficulty in Backus-Naur Form. In practice, such defi

40、nitions are often left incomplete and the rules qualified informally in English. b) Dejining something by specifying the few exceptional cases. An Algol end-comment ends at the first end, else or semicolon. A rule like this cannot be expressed concisely or clearly in Backus-Naur Form and is also usu

41、ally specified informally in English. c) Including comments. Programming languages and other structures with a complicated syntax need many rules to define them. The syntax will be clearer if explanations and cross-references can be provided; accordingly Extended BNF contains a comment facility so t

42、hat ordinary text can be added to a syntax for the benefit of a human reader without affecting the formal meaning of the syntax. d) Meta-identi$el: A meta-identifier (the name of a non-terminal symbol in the language) need not be a single word or enclosed in brackets because there is an explicit con

43、catenate symbol. This also ensures that the layout of a syntax (except in a terminal symbol) does not affect the language being defined. e) Extensions. A user may wish to extend Extended BNF. A special-sequence is provided for this purpose, the format and meaning of which are not defined in the stan

44、dard except to ensure that the start and end of an extension can always be seen easily. Various possible extensions are outlined in the following paragraphs. Limitations and extensions The main limitation of Extended BNF is that the language being defined needs to be linear, i.e. the symbols in a se

45、ntence of the language can be placed in an ordered sequence. For example knitting patterns and recipes in cooking are linear languages, but electric circuit diagrams are not. A further limitation is that Extended BNF is inadequate for defining more complex forms of grammars. Such facilities were not

46、 provided because it was thought the main need was to define a notation sufficient for the simpler and commoner requirements. Instead Extended BNF has been designed so that various extensions can be made in a natural way. There are two simple ways of extending the standard metalanguage. Firstly, the

47、 special-sequence concept provides a basic framework for any extension, the format between the special-sequence-characters being almost completely arbitrary. This method would be suitable for an action grammar, i.e. one specifying actions that are to take place as a sentence is parsed. Secondly, a m

48、eta-identifier can never be followed immediately by a left parenthesis in the standard metalanguage; thus another method of extending the metalanguage is to define the syntax and meaning of a meta-identifier followed by a sequence of parameters enclosed in parentheses. This would be reasonable in an

49、 attribute grammar where the rules ensure consistency between different parts of a sentence in the language being defined. More complicated extensions are also possible. Annex A suggests how Extended BNF might be extended to define a two-level grammar. . . . VIII INTERNATIONAL STANDARD ISO/IEC ISO/IEC 14977:1996(E) Information technology - Syntactic metalanguage - Extended BNF 1 Scope This International Standard defines a notation, Extended BNF, for specifying the syntax of a linear sequence of symbols. It defines both the logical structure of the notation and its graph