Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 10279-94 and Amendment 1:1996 – Standard for Full BASIC Programming Language
Technical Overview and Compliance Guide for ISO/IEC 10279
International standard IEC 10279-94 (also published jointly as ISO/IEC 10279:1991 and its Amendment 1:1996) provides a definitive specification for the Full BASIC programming language. Originally developed to resolve fragmentation among vendor-specific BASIC dialects, the standard establishes a consistent minimal set and a full language profile that includes advanced features such as structured control constructs, subprograms, and—after the 1996 amendment—graphics primitives. This article offers an in‑depth look at the scope, technical requirements, implementation considerations, and compliance procedures defined by the standard.
Scope of the Standard
IEC 10279-94 defines the syntax, semantics, and constraints for the Full BASIC language. The document covers two conformance levels:
- Minimal BASIC – Contains only the core constructs necessary for elementary programming.
- Full BASIC – Extends the minimal set with structured programming elements (multi‑line blocks, modules), array operations, file input/output, and error handling.
Amendment 1:1996 (commonly referred to as amd1-1996) introduced a complete graphics subsystem, enabling applications to create and manipulate graphical windows, draw geometric shapes, and manage events. The amendment also clarified ambiguity in floating‑point arithmetic and defined an interoperable numeric format for saved data.
Tip: Though the standard is aging, its well‑defined syntax makes it ideal for embedded systems and education, where predictable behavior is more important than modern feature sets.
Technical Requirements
The core language specification is divided into several categories. The table below summarises the most significant elements and the level at which they must be implemented for compliance.
| Category | Key Elements | Requirement Level (Full BASIC) |
|---|---|---|
| Data Types | numeric (integer and real), string, boolean | Mandatory |
| Control Structures | IF‑THEN‑ELSE (single + block), SELECT CASE, FOR, DO (WHILE/UNTIL) | Mandatory |
| Subprograms | FUNCTION / SUB with local variables and parameter passing | Mandatory |
| Graphics (Amd 1) | WINDOW, PLOT, DRAW, BUTTON, and event handling primitives | Optional (but required for Full BASIC compliance after amendment) |
| File I/O | sequential and direct access, internal files, structured data | Mandatory |
| Array Operations | multidimensional arrays, array slicing, matrix arithmetic | Mandatory |
Data Types and Expressions
The standard mandates two floating‑point precision levels (REAL vs. INTEGER) and a STRING type with dynamic length. Boolean values are not first‑class data but are implicitly created by relational operators; implementations must treat true and false consistently in conditional expressions. The 1996 amendment further tightened the rules for decimal rounding and introduced an extended string library.
Structured Programming Constructs
Full BASIC requires multi‑line control blocks. For example, the syntax IF condition THEN … ELSE … END IF is compulsory, eliminating traditional line‑numbering requirements for flow control. The SELECT CASE construct is mandatory, as are loops using FOR and DO. All loops support early exit with EXIT.
Warning: Translators migrating code from older BASIC variants may encounter line‑number references that are incompatible with the block‑oriented syntax of IEC 10279-94. Careful restructuring is required to achieve compliance.
Graphics Subsystem (Amendment 1:1996)
The amendment adds a device‑independent graphics model. Programs can create windows (WINDOW), set colors, draw lines and circles (PLOT LINES, DRAW CIRCLE), and respond to mouse/keyboard events. The graphics environment is event‑driven; compliance requires that the runtime queue and dispatch events according to the standard’s semaphore protocol.
Implementation Highlights
When implementing a Full BASIC system, developers should pay attention to the following aspects to ensure conformance:
- Data storage – Numeric values must be stored in a format that can be exchanged between compliant implementations. The standard recommends IEEE 754 single or double precision.
- Namespace management – Full BASIC requires a module system where subprograms can be grouped and used with the
EXTERNALkeyword. - Graphics portability – The graphics primitives are defined in terms of a logical coordinate system; implementations must map logical to physical pixels consistently.
- Error handling – A mandatory set of error codes (e.g., for division by zero, type mismatch) must be supported, and programs can trap these with
ON ERROR.
Benefit: By following the Full BASIC rules, developers can write applications that run unchanged across multiple platforms that conform to the standard, significantly reducing porting effort.
Compliance and Validation
Conformance to IEC 10279-94 (as amended) can be tested using reference interpreter suites published by ISO or national testing bodies. The compliance process typically involves:
- Functional tests – Running a provided set of 100+ kernels covering each syntactic and semantic requirement.
- Boundary tests – Validating overflow, string length limits, and recursion depth handling.
- Graphics tests – Verifying window creation, drawing outputs, and event loop integrity (added with Amendment 1).
Implementers must document which parts of the standard are supported (e.g., minimal or full, graphics included). Products claiming Full BASIC compliance must satisfy all mandatory requirements from the base document and the amendment.
Non‑compliance risk: Omitting required error messages or implementing a non‑standard
FOR loop termination can lead to rejection during certification, especially in safety‑critical projects where the standard is referenced by procurement regulations. Frequently Asked Questions
Q: What is the difference between IEC 10279-94 and the earlier minimal BASIC standard (ISO 6373)?
A: IEC 10279-94 (Full BASIC) substantially expands the older minimal standard by adding block structures, file handling, and subprograms. The two standards are compatible: any program written in minimal BASIC should also run in a Full BASIC environment provided no conflicting syntax is used.
A: IEC 10279-94 (Full BASIC) substantially expands the older minimal standard by adding block structures, file handling, and subprograms. The two standards are compatible: any program written in minimal BASIC should also run in a Full BASIC environment provided no conflicting syntax is used.
Q: Is Amendment 1:1996 mandatory for compliance with IEC 10279-94?
A: Products claiming Full BASIC conformance without graphics need only support the base standard. If the product claims graphics capability, it must implement all mandatory graphics elements defined in the amendment. Many supply contracts require the graphics subsystem, so it is usually included.
A: Products claiming Full BASIC conformance without graphics need only support the base standard. If the product claims graphics capability, it must implement all mandatory graphics elements defined in the amendment. Many supply contracts require the graphics subsystem, so it is usually included.
Q: How can I test my interpreter for compliance?
A: The recommended validation suite is distributed by the ISO/IEC Joint Technical Committee (JTC 1) as “Basic Conformance Test Suite” (BCTS). It comprises over 150 test programs covering every clause of the standard. Automated testing tools are available from several national standards bodies.
A: The recommended validation suite is distributed by the ISO/IEC Joint Technical Committee (JTC 1) as “Basic Conformance Test Suite” (BCTS). It comprises over 150 test programs covering every clause of the standard. Automated testing tools are available from several national standards bodies.
Q: Does IEC 10279-94 support object‑oriented programming?
A: No. The standard predates widespread object‑oriented concepts. Full BASIC relies on structured procedural programming with subprograms. Some later implementations extend the language with OOP features, but such extensions are not part of the international standard.
A: No. The standard predates widespread object‑oriented concepts. Full BASIC relies on structured procedural programming with subprograms. Some later implementations extend the language with OOP features, but such extensions are not part of the international standard.
This article is based on the 1994 edition of IEC 10279 and Amendment 1:1996. For the latest information, consult the ISO/IEC JTC 1 website or your national standards body. © 2026 International Standards Documentation.