
PL/0 - Wikipedia
PL/0 is a programming language, intended as an educational programming language, that is similar to but much simpler than Pascal, a general-purpose programming language. It serves as an example of how to construct a compiler. It was originally introduced in the book, Algorithms + Data Structures = Programs, by Niklaus Wirth in 1976. It features ...
PL/0 语言简介、PL/0 文法_编译原理中什么是pl0语言-CSDN博客
PL/0 程序设计语言是一个较简单的语言,它以赋值语句为基础,构造概念有 顺序、条件和重复(循环)三种。 PL/0 有子程序概念,包括过程定义(可以嵌 套)与调用且有局部变量说明。 PL/0 中唯一的数据类型是整型,可以用来说明 该类型的常量和变量。 当然 PL/0 也具有通常的算术运算和关系运算。 PL/0 是一个小巧的高级语言。 虽然它只有整数类型,但它是相当完全的可嵌套 …
PL/0 – Pascal for small machines
PL/0 is a small educational language designed and implemented by Wirth to be used as an example of compiler development. The language was presented by Niklaus Wirth in his book “Algorithms + Data Structures = Programs” (1975).
CS485 Project - PL/0 Compiler - wmich.edu
PL/0 is a small example language created and used by Niklaus Wirth in his book "Algorithms + Data Structures = Programs". The book gives a PL/0 compiler written in Pascal. The compiler program can be compiled using a Pascal compiler (for example, Turbo Pascal which runs in MS-DOS and is freely available on the Web).
Wirth's PL/0 - implementation of programming language PL/0 ...
Implementation of programming language PL/0 A reference PL/0 compiler, published by Niklaus Wirth in 1975-76 in “Algorithms + Data Structures = Programs” and “Compilerbau” books and updated in the following editions of the latter book.
PL/0 - Progopedia - Encyclopedia of Programming Languages
PL/0 is a small educational language used as an example of compiler development. The language was presented by Niklaus Wirth in his book “Algorithms + Data Structures = Programs” (1975). His later book “Compilerbau” (“Compiler Construction”, 1976) provided a full source code of PL/0 compiler written in Pascal .
CSE 401: PL/0 - Project Description - University of Washington
The PL/0 language spec allows procedure names to be arbitrarily long, and requires that they be unique only within their scope (just like other identifiers). These are the rules you should enforce in your syntactic/semantic analysis phases.