PL360

PL360 (or PL/360) is a system programming language designed by Niklaus Wirth and written by Niklaus Wirth, Joseph W. Wells, Jr., and Edwin Satterthwaite, Jr. for the IBM System/360 computer at Stanford University. A description of PL360 was published in early 1968, although the implementation was probably completed before Wirth left Stanford in 1967.[1]

Description

PL/360 is a one pass compiler with a syntax similar to Algol that provides facilities for specifying exact machine language instructions and registers similar to assembly language, but also provides features commonly found in high-level languages, such as complex arithmetic expressions and control structures. Wirth used PL360 to create Algol W.

Data types are:[2]:p.2–1

  • Byte or character – a single byte.
  • Short integer – 2 bytes, interpreted as an integer in two's complement binary notation.
  • Integer or logical – 4 bytes, interpreted as an integer in two's complement binary notation.
  • Real – 4 bytes, interpreted as a base-16 short floating-point number.
  • Long real – 8 bytes, interpreted as a base-16 long floating-point number.

Registers can contain integer, real, or long real.

Individual System/360 instructions can be generated inline using the PL360 "function statement" that defined an instruction by format and operation code. Function arguments were assigned sequentially to fields in the instruction. Examples are:

definitionreference
UNPK(10,#F300)UNPK(3,7,B2,worker)
EX(2,#4400)EX(R1,MVC(0,lines,buffer))note nested reference

Example

R0, R1, and R2, and FLAG are predeclared names.

    BEGIN INTEGER BUCKET;
         IF FLAG THEN
         BEGIN BUCKET := R0; R0 := R1; R1 := R2;
               R2 := BUCKET;
         END ELSE
         BEGIN BUCKET := R2; R2 := R1; R1 := R0;
              R0 := BUCKET;
         END
         RESET(FLAG);
    END

Implementation

Wirth was at Stanford between 1963 and 1967, during the earlier part of which he was developing his Euler compiler and interpreter, the sources of which are dated 1965. Also in 1965, Stanford updated their drum-based Burroughs B5000 to a disk-based B5500.

Since the target IBM S/360 (which was to replace an existing IBM 7090) was not installed until 1967, the initial implementation of PL360 was written in ALGOL and tested on Stanford's B5500. Once working, the compiler was then recoded in PL360 itself, recompiled on the Burroughs system, and moved as a binary to the S/360.

It is notable that the B5500 is itself programmed in a high-level ALGOL-derived language (ESPOL), and PL360 was intended to bring a comparable facility to the IBM mainframe architecture, although it was lacking major facilities of both Assembler F and ESPOL. This intent was largely ignored, with programmers continuing to use implementations of IBM's macro assemblers.

However, in the early 1970s, PL360 was extended to provide more capabilities, and was the programming language of choice for developing SPIRES, Stanford's Database Management System.

gollark: Probably not though.
gollark: Either that or it is nonrandom and deliberately tries to support people who would otherwise leave.
gollark: Random chance!
gollark: People probably do want hatchlings more than uninfluencable-now eggs.
gollark: Thanks for the massbreed! AP times are down.

See also

References
  1. Wirth, Niklaus (January 1968). "PL360, a Programming Language for the 360 Computers". Journal of the ACM. 15 (1): 34–74. doi:10.1145/321439.321442.
  2. Stanford University. "P L 3 6 0 REFERENCE MANUAL". Retrieved October 21, 2012.


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.