PL/I (pronounced "pee el one") is a programming language intended and useful for both scientific/engineering and business use. It has a very large vocabulary of built-in functions. In fact, there is probably no one compiler that has the full standard of keywords available. PL/I compilers are normally subsets of the language that specialize in various fields. The language syntax is English-like, clean and powerful. It can describe complex formats of data easily, and there is a wide set of functions available to verify and manipulate them. It is a very good language for data processing. PL/I supports recursion and structured programming.
Common facts about the language:
- Free form syntax
- Case insensitive keywords
- Passes by reference by default
- Supports complex structure declarations with unions
- Built-in support for a slew of data types, including two types of strings
- Several kinds of dynamic storage allocation.
History of PL/I
PL/I was developed by IBM as part of the development of the System 360. Prior to the introduction of the System 360, IBM made several different incompatible models of mainframes for different purposes: some mainframes were designed for business use, others for scientific use. The goal of the System 360 project was to develop one series of compatible models to replace all the previous models, and which could be used equally well for commercial or scientific use.
Not only did business and scientific users use different machines; they also used different languages. Business users mainly used COBOL, while scientific users used Fortran. The goal of PL/I was to develop a single language usable for both business and scientific purposes. Another goal was to add structured programming constructs derived from ALGOL, which neither COBOL nor Fortran supported (at the time). PL/I was designed by a committee drawn from IBM programmers and users drawn from across the United States, working over several months. The original goal was to have PL/I ready for use by the time of the launch of the System 360; but unfortunately this deadline could not be met.
The language was originally to be called NPL, for "New Programming Language"; but that abbreviation could not be used because it was the name of the National Physical Laboratories in England. So PL/I was chosen instead.
The PL/I language did not have the success that was originally hoped for. This was due to several factors. Most importantly, the language was highly complex, which made it difficult to implement on time. This was probably due to it being designed by a committee, and the desire to supply the needs of very different types of users (business and scientific users). Its delay, its complexity, and the low quality of early versions of IBM's PL/I compiler discouraged users to switch from COBOL or Fortran. It contained many features users rarely used, such as multithreading support, and which added corresponding cost and complexity to the compiler.
Another major problem was that instead of noticing features that would make their job easier, scientific (FORTRAN) programmers of the time had the opinion that it was a business language, while business (COBOL) programmers looked on it as a scientific language!
PL/I was probably the first commercial language where the compiler was written in the language to be compiled. (The experimental language NELIAC beat them to it by at least five years, and there may have been others.)
That is not to say that PL/I was not used. It recieved significant use in business data processing, and also for more general programming use. The Multics project, the first to develop an operating system in a high level language, used PL/I. A subset of PL/I, PL/M, was used to write CP/M.
The first online Airline Reservation System (SABRE) was written (or at least supposed to be written) in PL/I.
Test: procedure options(main); declare [[My_String]] char(20) varying initialize('Hello, world!'); put skip list([[My_String]]); end Test;
ANSI X3.74-1987 (R1998) Title: Information Systems - Programming Language - PL/I General-Purpose Subset