1、I N TE R N AT IO N A L STANDARD ISOIIEC 10279 First edition 1991 -10-15 (Reaff i r med 2004) Information technology - Programming languages - Full BASlC Technologies de /information - Larigages de programmation - Full BASIC National Standard of Canada CAN/CSA-ISO/IEC-lO279-94 International Standard
2、ISO/IEC 10279:1991 has been adopted, without modification, as CAN/CSA-ISO/IEC- 10279 -94, which has been approved as a National Standard of Canada by the Standards Council of Canada. November 1994 Reference number ISOAEC 10279:1991 (E) ISOllEC 10279:1991 (E) Foreword IS0 (the International Organizat
3、ion for Standardization) and IEC (the fnternational Electrotechnical Commission) form the specialized system 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 respect
4、ive organization to deal with particular fields of technical activity. IS0 and IEC technical com- mittees collaborate in fields of mutual interest. Other international or- ganizations, governmental and non-governmental, in liaison with IS0 and IEC, also take part in the work. In the field of informa
5、tion technology, IS0 and IEC have estabfished a joint technical committee, ISO/iEC JTC 1. DraR International Standards adopted by the joint technicaf committee are circulated to national bod- ies for voting. Publication as an International Standard requires ap- proval by at least 75 % of the nationa
6、l bodies casting a vote. fnternational Standard ISO/IEC 10279 was prepared by Joint Technical Committee ISOAEC JTC 1, Information technology. Annexes A and E3 are for information only. 8 ISO/IEC 1991 All rights reserved. No part of thls publication may be reproduced or utilized in any form or by any
7、 means, electronic or mechanical, including photocopying and microfilm, without permission In writing from the publisher. Printed In Switzerland ISO/IEC Copyright Office Case Postale 56 CH-1211 Geneve 20 Switzerland ii INTERNATIONAL STANDARD ISO/IEC 10279:1991() nformation technology - Programming l
8、anguages - Full 3ASIC 1 Scope This International Standard specifies the programming language Full BASIC and is derived from the American National Standard X3.113-1987. For details of the syntax and semantics see ANSI X3.113-1987 which specifies the syntax of programs written in BASIC, including core
9、 8ASIC and various extensions thereto; the formats of data and the minimum precision and range of numeric representations and the minimum length and set of characters in strings that are acceptable as input to an automatic data processing system being controlled by a program written in BASIC; the fo
10、rmats of data and the minimum precision and range of numeric representations and the minimum length and set of characters in strings that can be generated as output by an automatic data processing system being controlled by a program written in BASIC; the semantic rules for interpreting the meaning
11、of a program written in BASIC; errors and exceptional circumstances to be detected and also the manner in which such errors and excepfional circumstances are to be handled This International Standard also refers to ECMA-116 for the specification of mini-graphics. Note: ECMA-116 is based on ANSI X3.1
12、13-1987. This International Standard specifies its own conformance subsets, which include those specified in ANSI X3.113- 1987 and ECMA-116. This International Standard is designed to promote the interchangeability of BASIC programs among a variety of automatic data processing systems. 2 Normative r
13、eferences The following standards contain provisions which, through reference in this text, constitute provisions of this International Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this Internationa
14、l Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. Members of IEC and of IS0 maintain registers of currently valid International Standards. ANSI X3.113-1987: information systems - programming languages - full BASIC. STANDAR
15、D ECMA-116: 1986, BASIC. I ISOIIEC 10279:1991 (E) 3 Technical content 3.1 Principal technical content Apart from the conformance rules the technical content of this International Standard is defined in part by Sections 3 to 16 of the ANSI X3.113-1987 (which will be referred to a ANS BASIC). The defi
16、nition of resewed wordin ANS BASIC Section 3.2 is for information only with respect to this International Standard. The technical content for the mini-graphics module of this International Standard is defined by Section 13 of ECMA-I 16. 3.2 Additional reserved words For the subset core, insert the f
17、ollowing paragraph after paragraph 6 of Subsection 4.4.2 of ANS BASIC. “The keywords ACCESS, AND, ANGLE, AREA, ARITHMETIC, ASK, AT, BASE, BEGIN, BREAK, CALL, CASE, CHAIN, CLEAR, CLIP, CLOSE, COLLATE, COLOR, DATA, DATUM, DESUG, DECIMAL, DECLARE, DEF, DEGREES, DEVICE, DIM, DISPLAY, DO, ELAPSED, ELSEIF
18、, END, ERASE, ERASABLE, EXIT, EXTERNAL, FILETYPE, FOR, FUNCTION, GO, GOSUB, GOTO, GRAPH, IF, IMAGE, INPUT, INTERNAL, IS, LENGTH, LET, LINE, LINES, LOOP, MARGIN, MAT, MISSING, NAME, NATIVE, NEXT, NUMERIC, OFF, ON, OPEN, OPTION, OR, ORGANIZATION, OUTIN, OUTPUT, POINT, POINTER, POINTS, PROGRAM, PROMPT,
19、 RADIANS, RANDOMIZE, READ, RECSIZE, RECTYPE, REST, RESTORE, RETURN, SAME, SELECT, SEQUENTIAL, SET, SE-TTER, SIZE, SKIP, STANDARD, STATUS, STEP, STOP, STREAM, STRING, STYLE, SUB, TAB, TEXT, THEN, THERE, TIMEOUT, TO, TRACE, UNTIL, USING, VARIABLE, VIEWPORT, WHILE, WINDOW, WITH, WRITE, and ZONEWIDTH sh
20、all not be used as identifiers.“ 4 Conformance There are two aspects of conformance to a set of modules in this International Standard: conformance by a program written in the BASIC language, and conformance by an implementation which processes such programs. The conformance requirements are structu
21、red so that any program conforming to a set of modules will produce the same results when executed by any implementation conforming to the same or an encompassing set of modules (though certain implementation-dependent features are noted in ANS BASIC Appendix C). 4.1 Modules The programming language
22、 defined by this International Standard is organized in a modular fashion. Conformance to this International Standard is defined with respect to particular sets of the following fifteen modules and combinations the reof: A cure module, which encompasses all programs whose syntax conforms to ANS BASI
23、C Sections 4 to 10, parts of ANS BASC Section 11 (excluding internal-format record and native-format record files), and ANS BASIC Section 12. A subsef core module, which encompasses all programs whose syntax conforms to ANS BASIC Sections 4 to 10 (except that a substitute definition of resewed worda
24、pplies - see 3.2), parts of ANS BASIC Section 1 I (excluding enhanced-internat and enhanced-native files), and ANS BASIC Subsection 12.2. (The subset core module is identical to the core module except that the list of reserved words is larger and exception handling is excluded.) An enhanced-internal
25、 file module, which encompasses all programs whose syntax conforms to the enhanced production rules in ANS BASIC Section 11 (lacking the prefix “N“), together with the core. An enhanced-internal file subset module, which encompasses all programs whose syntax conforms to the enhanced production rules
26、 in ANS BASIC Section 1 I (lacking the prefix “W, together with the subset cure. 2 ISO/IEC 10279:1991 (E) f An enhanced-native file module, which encompasses all programs whose syntax conforms to the enhanced native production rules in ANS BASIC Section 11 (indicated with the prefix “N“), together w
27、ith the core. An enhanced-native file subset module, which encompasses all programs whose syntax conforms to the enhanced native production rules in ANS BASIC Section 11 (indicated with the prefix “N“), together with the subset core. A graphics module, which encompasses all programs whose syntax con
28、forms to ANS BASIC Section 13, together with the core. A graphics subset module, which encompasses all programs whose syntax conforms to ANS BASIC Section 13, together with the subset core. A mini graphics module, which encompasses all programs whose syntax conforms to ECMA-116 Section 13 (see Annex
29、 B), together with the core. A mini graphics subset module, which encompasses all programs whose syntax conforms to ECMA-116 Section 13 (see Annex B), together with the subset core. A real-time module, which encompasses all programs whose syntax conforms to ANS BASIC Section 14, together with the co
30、re. A real-time subset module, which encompasses all programs whose syntax conforms to ANS BASIC Section 14, together with the subset core. A fixed decimal module, which encompasses all programs whose syntax conforms to ANS BASIC Section 15, together with ?he core. A fixed decimal subset module, whi
31、ch encompasses at1 programs whose syntax conforms to ANS BASIC Section 15, together with the subset cure. An editing module, which encompasses all unsorted programs and editing commands whose syntax conforms to ANS BASIC Section 16. In addition, the Conformance Modules shall include those described
32、in ANS X3-113, Section 2, and in ECMA-116, Section 2. (Note: See Annex A for details on the relationship between these conformance modules and the conformance modules defined in ANS X3-113 and ECMA-116.) 4.2 Program conformance A program conforms to a set of modules in this International Standard on
33、ly when the program and each statement or other syntactic element contained therein is syntactically valid according to the syntactic rules specified by this International Standard as belonging to that set; the program as a whole violates none of the global constraints imposed by this International
34、Standard on the application of the syntactic rules. 3 ISO/IEC 10279:1991 (E) 4.3 Imp lernentatio n conformance An implementation conforms to a set of modules in this International Standard only when it accepts and processes all programs conforming to that set of modules in this International Standar
35、d; it reports reasons for rejecting any program which does not conform to that set of modules in this International Standard; it interprets errors and exceptional circumstances according to the specifications of this I nt e m a tio nal Stand a rd ; it interprets the semantics of each statement of a
36、conforming program according to the specifications in this lnternational Standard; it interprets the semantics of a conforming program as a whole according to the specifications in this International Standard; it accepts as input, manipulates, and can generate as output numbers of at least the preci
37、sion and range specified in this International Standard: it accepts as input, manipulates, and can generate as output strings of at least the length and composed of at least those characters specified in this International Standard; it is accompanied by documentation available to the user that descr
38、ibes the actions taken in regard to features referred to as “undefined“ or “implementation-defined“ in this International Standard; it is accompanied by documentation available to the user that describes and identifies all enhancements to the language defined in this International Standard. This Int
39、ernational Standard makes no requirement concerning the interpretation of the semantics of any statement or program as a whole that does not conform to this International Standard. In addition, an implementation conforms to the editing requirements of this International Standard if it accepts and pr
40、ocesses unsorted programs and editing commands according to the specifications in ANS BASIC Section 16. 4.4 Errors This International Standard does not include specific requirements for reporting syntactic errors in the text of a program. Implementations conforming to a set of modules in this Intema
41、tional Standard may accept programs written in an enhanced language without having to report all constructs not conforming to that set of modules. Whenever a statement, or other program element, does not conform to the syntactic rules given herein, and that statement, or program element, does not ha
42、ve a clear, well-documented implementation-defined meaning, an error shall be reported. Errors shall be reported in a clear and well-documented way, and whenever feasible the implementation should indicate the erroneous statement and the position of the error within the statement. 4.5 Exceptions An
43、exception is a circumstance arising in the course of execution of a program when an implementation recognizes that the semantic rules of this International Standard cannot be followed or that some resource constraint is about to be exceeded. All exceptions described in this International Standard sh
44、all be detected, reported, and processed when they occur, unless some mechanism provided in ANS BASIC Subsection 12.1 or in an enhancement to this International Standard has been invoked by the user to handle exceptions. In the absence of programmer-specified recovery procedures, exceptions shall be
45、 handled by the recovery procedures specified in this International Standard. If no recovery procedure is specified in this International 4 ISO/IEC 10279:1991 (E) Standard, or if restrictions imposed by the hardware or the operating environment make it impossible to follow the procedure specified in
46、 this International Standard, then the way in which the exception is handled depends on the context. If the exception occurred in an invocation of a function, picture, or subprogram, then the exception is “propagated back“ to the invoking statement in the invoking program unit (see ANS BASIC Subsect
47、ion 12.1). If this propagation procedure reaches the main-program or a parallel-section, or if the exception occurred in the main- program or a parallel-section, then the exception shall be handled by terminating the program or, in the case of real- time-programs, the parallel-section, generating th
48、e exception. The way in which the default exception handling mechanism reports an exception is implementation-defined, except that the contents of the report shall identify at least the original exception code and the line number of the line in which the original exception occurred. Except in the ca
49、se of files, when several exceptions are caused by the execution of a single statement of a program, this International Standard does not specify an order in which these exceptions shall be detected, reported, or processed. If an implementation determines that a particular statement in a conforming program will always cause an exception when executed, the implementation may issue a warning to the user. Nonetheless, the implementation shall accept and execute the program, according to the normal semantic rules specified herein. 5 ISO/IEC 10279:1991 (E) Annex A (i nf ormat ive) Relationship o
