Wirth syntax notation

The Wirth syntax notation (WSN) is a variant of the Extended Backus-Naur form developed by Niklaus Wirth for the definition of Pascal and subsequent languages including Modula-2 and Oberon. WSN uses distinct symbols for repetition and optionality: while EBNF uses curly braces and square brackets, WSN uses the repetition symbol { } for "zero or more" and the option symbol [ ] for "optional," but with a different typographic convention that emphasizes the production rule structure. The notation was designed to be typeset cleanly in academic papers and language manuals, reflecting Wirth's commitment to clarity in both language design and language documentation.

WSN is formally equivalent to EBNF and to standard Backus-Naur form: any grammar written in one notation can be mechanically translated into the other. The differences are notational, not mathematical. Wirth's choice of symbols was guided by readability concerns specific to the printed page, not by any extension of expressive power. The notation is documented in the Pascal User Manual and Report, and it became the standard for language definition in the Pascal tradition.

The significance of WSN is not technical but cultural. It represents a design philosophy — Wirth's philosophy — that values simplicity and clarity over generality and power. The notation is minimal: it provides exactly the constructs needed to describe Pascal-like languages and nothing more. This minimalism is consistent with Wirth's broader design ethic, visible in his languages, his compilers, and his teaching. The Wirth syntax notation is the notation of a designer who believes that a good language is one that can be described simply, and that a good description is one that a student can read in an afternoon.

The Wirth syntax notation is a footnote in the history of formal grammar, but it is a revealing footnote. It shows that notation choices are not neutral: they encode values. Wirth's brackets and braces encode a pedagogy — the belief that a language specification should be a teaching document, not merely a contract between designer and implementer. The ISO 14977 standard for EBNF, by contrast, encodes a bureaucracy: the belief that a language specification should be unambiguous, complete, and suitable for committee review. Both are legitimate. But they are not the same, and the choice between them is a choice about what a programming language is for.