Search results
Programming language. lists. Alphabetical. Categorical. Chronological. Generational. v. t. e. This is an index to notable programming languages, in current or historical use. Dialects of BASIC, esoteric programming languages, and markup languages are not included.
- List of Programming Languages by Type
A concatenative programming language is a point-free...
- F Sharp
Language overview Functional programming. F# is a strongly...
- Generational
This is a "genealogy" of programming languages. Languages...
- Elixir
Elixir is a functional, concurrent, high-level...
- Cobra
Free and open-source software portal; Cobra is a...
- Timeline
none (unique language) 1955 Address (programming language)...
- List of Stylesheet Languages
The following is a list of style sheet languages. Standard....
- List of Programming Languages by Type
- Early History
- Goals and Principles
- Language Summary
- Standardization
- Implementations
- PL/I Dialects
- Usage
- Evolution of The PL/I Language
- Criticisms
- Special Topics in PL/I
In the 1950s and early 1960s, business and scientific users programmed for different computer hardware using different programming languages. Business users were moving from Autocoders via COMTRAN to COBOL, while scientific users programmed in Fortran, ALGOL, GEORGE, and others. The IBM System/360 (announced in 1964 and delivered in 1966) was desig...
The goals for PL/I evolved during the early development of the language. Competitiveness with COBOL's record handling and report writing was required. The language's scope of usefulness grew to include system programming and event-driven programming.Additional goals for PL/I were: 1. Performance of compiled code competitive with that of Fortran (bu...
The language is designed to be all things to all programmers.[vague] The summary is extracted from the ANSI PL/I Standardand the ANSI PL/I General-Purpose Subset Standard. A PL/I program consists of a set of procedures, each of which is written as a sequence of statements. The %INCLUDEconstruct is used to include text from other sources during prog...
Language standardization began in April 1966 in Europe with ECMA TC10. In 1969 ANSI established a "Composite Language Development Committee", nicknamed "Kludge", later renamed X3J1 PL/I. Standardization became a joint effort of ECMA TC/10 and ANSI X3J1. A subset of the GY33-6003 document was offered to the joint effort by IBM and became the base do...
IBM PL/I F and D compilers
PL/I was first implemented by IBM, at its Hursley Laboratories in the United Kingdom, as part of the development of System/360. The first production PL/I compiler was the PL/I F compiler for the OS/360 Operating System, built by John Nash's team at Hursley in the UK: the runtime library team was managed by I.M. (Nobby) Clarke. The PL/I F compiler was written entirely in System/360 assembly language.Release 1 shipped in 1966. OS/360 is a real-memory environment and the compiler was designed fo...
Multics PL/I and derivatives
Compilers were implemented by several groups in the early 1960s. The Multics project at MIT, one of the first to develop an operating system in a high-level language, used Early PL/I (EPL), a subset dialect of PL/I, as their implementation language in 1964. EPL was developed at Bell Labs and MIT by Douglas McIlroy, Robert Morris, and others. Initially, it was developed using the TMG compiler-compiler. The influential Multics PL/I compilerwas the source of compiler technology used by a number...
IBM PL/I optimizing and checkout compilers
The PL/I Optimizer and Checkout compilers produced in Hursley support a common level of PL/I language and aimed to replace the PL/I F compiler. The checkout compiler is a rewrite of PL/I F in BSL, IBM's PL/I-like proprietary implementation language (later PL/S). The performance objectives set for the compilers are shown in an IBM presentation to the BCS.The compilers had to produce identical results – the Checkout Compiler is used to debug programs that would then be submitted to the Optimize...
PL/S, a dialect of PL/I, initially called BSL was developed in the late 1960s and became the system programming language for IBM mainframes. Almost all IBM mainframe system software in the 1970s an...Two dialects of PL/I named PL/MP (Machine Product) and PL/MI (Machine Interface) were used by IBM in the system software of the System/38 and AS/400 platforms. PL/MP was used to implement the so-ca...PL/8 (or PL.8), so-called because it was about 80% of PL/I, was originally developed by IBM Research in the 1970s for the IBM 801 architecture. It later gained support for the Motorola 68000 and Sy...PL/I implementations were developed for mainframes from the late 1960s, mini computers in the 1970s, and personal computers in the 1980s and 1990s. Although its main use has been on mainframes, there are PL/I versions for DOS, Microsoft Windows, OS/2, AIX, OpenVMS, and Unix. It has been widely used in business data processingand for system use for ...
This article uses the PL/I standard as the reference point for language features. But a number of features of significance in the early implementations were not in the Standard; and some were offered by non-IBM compilers. And the de facto language continued to grow after the standard, ultimately driven by developments on the Personal Computer.
Implementation issues
Though the language is easy to learn and use, implementing a PL/I compiler is difficult and time-consuming. A language as large as PL/I needed subsets that most vendors could produce and most users master. This was not resolved until "ANSI G" was published. The compile time facilities, unique to PL/I, took added implementation effort and additional compiler passes. A PL/I compiler was two to four times as large as comparable Fortran or COBOL compilers, and also that much slower—supposedly off...
Programmer issues
Many programmers were slow to move from COBOL or Fortrandue to a perceived complexity of the language and immaturity of the PL/I F compiler. Programmers were sharply divided into scientific programmers (who used Fortran) and business programmers (who used COBOL), with significant tension and even dislike between the groups. PL/I syntax borrowed from both COBOL and Fortran syntax. So instead of noticing features that would make their job easier, Fortran programmers of the time noticed COBOL sy...
Storage classes
PL/I provides several 'storage classes' to indicate how the lifetime of variables' storage is to be managed – STATIC, AUTOMATIC, CONTROLLED, and BASED. The simplest to implement is STATIC, which indicates that memory is allocated and initialized at load-time, as is done in COBOL "working-storage" and early Fortran. This is the default for EXTERNAL variables.PL/I's default storage class for INTERNAL variables is AUTOMATIC, similar to that of other block-structured languages influenced by ALGOL...
Storage type sharing
There are several ways of accessing allocated storage through different data declarations. Some of these are well defined and safe, some can be used safely with careful programming, and some are inherently unsafe and/or machine dependent.: pp.262–267, 178–180 Passing a variable as an argument to a parameter by reference allows the argument's allocated storage to be referenced using the parameter. The DEFINED attribute (e.g. DCL A(10,10), B(2:9,2:9) DEFINED A) allows part or all of a variable'...
ON-units and exception handling
When PL/I was designed, programs only ran in batch mode, with no possible intervention from the programmer at a terminal. An exceptional condition such as division by zero would abort the program yielding only a hexadecimal core dump. PL/I exception handling, via ON-units, allowed the program to stay in control in the face of hardware or operating system exceptions and to recover debugging information before closing down more gracefully. As a program became properly debugged, most of the exce...
- 1964; 59 years ago
People also ask
How many programming languages are there?
How many PL/I programmers are there?
Is PL/I a good programming language?
Is PL/I a multi-processing language?
List of audio programming languages. List of BASIC dialects. List of C-family programming languages. List of CLI languages. List of concurrent and parallel programming languages. List of educational programming languages. Generational list of programming languages. List of JVM languages. List of Lisp-family programming languages.
Combining and averaging information from various internet sites, stackify.com reported the ten most popular programming languages (in descending order by overall popularity): Java, C, C++, Python, C#, JavaScript, VB .NET, R, PHP, and MATLAB.
Timeline of programming languages; List of programming languages; List of programmers