Pascal (programming language)
From Wikipedia, the free encyclopedia
Pascal is an imperative computer programming language, developed in 1970 by Niklaus Wirth as a language particularly suitable for structured programming. A derivative known as Object Pascal was designed for object oriented programming.
Paradigm: | imperative, structured |
---|---|
Appeared in: | 1970, last revised 1992 |
Designed by: | Niklaus Wirth |
Typing discipline: | static, strong, safe |
Major implementations: | CDC 6000, PASCAL-P, PDP-11, PDP-10, IBM System/370, HP, GNU |
Dialects: | UCSD, Borland, Turbo |
Influenced by: | ALGOL |
Influenced: | Modula-2, Ada, Delphi, Chrome, SCAR |
Contents |
[edit] History
Pascal is based on the ALGOL programming language and named in honour of mathematician and philosopher Blaise Pascal. Wirth subsequently developed Modula-2 and Oberon, languages similar to Pascal.
Initially, Pascal was a language intended to teach students structured programming, and generations of students have "cut their teeth" on Pascal as an introductory language in undergraduate courses. Variants of Pascal are still widely used today, for example Free Pascal can be used in both 32 and 64 bit formats, and all types of Pascal programs can be used for both education and software development.
Parts of the original Macintosh operating system were hand-translated into Motorola 68000 assembly language from the Pascal code used in the Apple Lisa (though later versions incorporated substantial amounts of C++ as well), and the primary high-level language used for development in the first couple of years of the Mac was Pascal. In addition, the popular typesetting system TeX was written by Donald E. Knuth in WEB, the original literate programming system using Pascal.
[edit] Implementations
The first Pascal compiler was designed in Zurich for the CDC 6000 series mainframe computer family, and it became operational in 1970. Niklaus Wirth reports that it had to be written in Fortran. Since about 1975, (with very limited exceptions) most Pascal Compilers have been self-hosting, that is, the compiler is itself written in Pascal, and the compiler is usually capable of recompiling itself when new features are added to the language, or when the compiler is to be ported to a new environment. The GNU Pascal compiler is one notable exception, being written in C.
The first successful port of the CDC Pascal compiler to another mainframe was completed by Welsh and Quinn at the Queen's University of Belfast in 1972. The target was the ICL 1900 computer.
The first Pascal compiler written in North America was constructed at the University of Illinois under Donald B. Gillies for the PDP-11 and generated native machine code.
In order to rapidly propagate the language, a compiler "porting kit" was created in Zurich that included a compiler that generated code for a "virtual" stack machine (i.e. code that lends itself to reasonably efficient interpretation), along with an interpreter for that code - the p-code system. Although the p-code was primarily intended to be compiled into true machine code, at least one system, the notable UCSD implementation, utilized it to create an interpretive system UCSD p-System. The P-system compilers were termed P1-P4, with P1 being the first version, and P4 being the last.
A version of the P4 compiler, which created native binaries, was released for the IBM System/370 mainframe computer by the Australian Atomic Energy Commission; it was called the "AAEC Pascal Compiler" after the abbreviation of the name of the Commission. A version of P4 from 1975-6 (based on its internal code, it probably should be called "P5") including source and binaries for the compiler and run-time library files for the PDP-10 mainframe may be downloaded from this link.
In the early 1980s, Watcom Pascal was developed, also for the IBM System 370.
IP Pascal was an implementation of the Pascal programming language using Micropolis DOS, but was moved rapidly to CP/M running on the Z80.
In the early 1980s, UCSD Pascal was ported to the Apple II and Apple III computers to provide a structured alternative to the BASIC interpreters that came with the machines.
Apple Computer created its own Lisa Pascal for the Lisa Workshop in 1982 and ported this compiler to the Apple Macintosh and MPW in 1985. In 1985 Larry Tesler, in consultation with Niklaus Wirth, defined Object Pascal and these extensions were incorporated in both the Lisa Pascal and Mac Pascal compilers.
In the 1980s Anders Hejlsberg wrote the Blue Label Pascal compiler for the Nascom-2. A reimplementation of this compiler for the IBM PC was marketed under the names Compas Pascal and PolyPascal before it was acquired by Borland. Renamed to Turbo Pascal it became hugely popular, thanks in part to an aggressive pricing strategy and in part to having one of the first full-screen Integrated development environments. In 1986 Anders ported Turbo Pascal to the Macintosh and incorporated Apple's Object Pascal extensions into Turbo Pascal. These extensions were then added back into the PC version of Turbo Pascal for version 5.5.
The inexpensive Borland compiler had a large influence on the Pascal community that began concentrating mainly on the IBM PC in the late 1980s. Many PC hobbyists in search of a structured replacement for BASIC used this product. It also began adoption by professional developers. Around the same time a number of concepts were imported from C in order to let Pascal programmers use the C-based API of Microsoft Windows directly. These extensions included null-terminated strings, pointer arithmetic, function pointers, an address-of operator and unsafe typecasts.
However, Borland later decided it wanted more elaborate object-oriented features, and started over in Delphi using the Object Pascal draft standard proposed by Apple as a basis. (This Apple draft is still not a formal standard.) Borland also called this Object Pascal in the first Delphi versions, but changed the name to Delphi Programming Language in later versions. The main additions compared to the older OOP extensions were a reference-based object model, virtual constructors and destructors, and properties. There are several other compilers implementing this dialect, see Object Pascal.
Turbo Pascal, and other derivatives with units or module concepts are modular languages. However, it does not provide a nested module concept or qualified import and export of specific symbols.
Super Pascal was a variant which added non-numeric labels, a return statement and expressions as names of types.
The universities of Zurich, Karlsruhe and Wuppertal have developed an EXtension for Scientific Computing (Pascal XSC) based on Oberon, which provides a free solution for programming numerical computations with controlled precision.
In 2005, at the Web 2.0 conference, Morfik Technology introduced a tool which allowed the development of Web applications entirely written in Morfik Pascal. Morfik Pascal is a dialect of Object Pascal, very close to Delphi.
[edit] Syntax
Pascal, in its original form, is a purely procedural language with the standard array of if
, while
, for
, and related constructs.
Syntactically, Pascal is distinguished from languages in the C family by a preference for (sometimes abbreviated) English keywords in places where C uses special punctuation; for example, Pascal's modulo operator is the keyword mod, but C's is the single character %
. Another, subtle, difference is the role of the semicolon. In Pascal semicolons separate statements (of any kind) within a compound statement, whereas in C semicolons are part of expression statements. This difference is not apparent when looking at a sequence of assignments and calls, because each line typically ends in a semicolon in either style. It manifests itself primarily in two situations, namely that there can never be a semicolon directly before else in Pascal (whereas a semicolon there is mandatory in C unless a block statement is used), and the last statement before an end is not required to be followed by a semicolon. Some Pascal programmers nevertheless as a matter of style put a semicolon on the last line before end, thereby formally inserting an empty statement at the end of the compound statement. Some educators discourage this style, worried that it may confuse students' perception of the formal role of the semicolon.
[edit] Hello world
All Pascal programs start with the "Program" keyword, an optional list of external file descriptors and then a statement block is indicated with the "begin
" and "end
" keywords. Semicolons separate statements, and the full stop ends the program (or unit). Letter case is ignored in Pascal source. Some compilers (Turbo Pascal among them) have made the Program keyword optional.
Here is an example of the source code in use for a very simple program:
program HelloWorld(output);
begin writeln('Hello, World!') end.
[edit] Data structures
Pascal has real, integer, character and boolean as the simple types, plus enumerations, a new type introduced with Pascal.
program myprog; var r: real; i: integer; c: char; b: boolean; e: (one, two, three, four, five);
A "subrange" of the "ordinal" types can be made.
var x: 1..10; y: 'a'..'z'; z: two..four;
Types can be built from other types by the type declaration.
program myotherprog; type x = integer; y = x; ...
Further, complex types can be constructed from simple types:
type a = array [1..10] of integer; b = record a: integer; b: char end; c = file of a;
As shown in the example above, Pascal files are sequences of components. Every file has a buffer variable which is denoted by f^. The procedures get (for reading) and put (for writing) move the buffer variable to the next element. Read is introduced such that read(f, x) is the same as x:=f^; get(f);. Write is introduced such that write(f, x) is the same as f^ := x; put(f); The type text is predefined as file of char. While the buffer variable could be used to inspect the next character that would be used (check for a digit before reading an integer), this concept leads to serious problems with interactive programs. Pascal 6000 and VAX Pascal had incompatible solutions for this problem and most other implementations omit the get and put procedures.
In Jensen & Wirth Pascal, strings are represented as packed arrays of chars; they therefore have fixed length and are usually space-padded. Later dialects commonly add a string type where the length of the contents can vary up to a declared maximum length. These are usually implemented by a length byte (limiting the maximum length to 255) and a fixed array of payload characters, and are therefore space-inefficient if the maximal length is seldom used in practice.
[edit] Pointers
Pascal supports the use of pointers:
type a = ^b; b = record a: integer; b: char; c: a end;
var pointer_to_b: a;
Here the variable pointer_to_b is a pointer to the data type b, a record. To create a new record and assign the values 10 and A to the fields a and b in the record, the commands would be;
new(pointer_to_b); pointer_to_b^.a := 10; pointer_to_b^.b := 'A'; pointer_to_b^.c := nil; ...
This could also be done using the with statement, as follows
new(pointer_to_b); with pointer_to_b^ do begin a := 10; b := 'A'; c := nil end; ...
Note that inside of the scope of the with statement, the compiler knows that a and b refer to the subfields of the record pointer pointer_to_b and not to the record b or the pointer type a.
Linked lists can be created by including a pointer type field (c) in the record (see also nil and null (computer)).
[edit] Control structures
Pascal is a structured programming language, meaning that the flow of control is structured into standard statements, ideally without 'go to' commands.
while a <> b do writeln('Waiting'); if a > b then writeln('Condition met') else writeln('Condition false'); for i := 1 to 10 do writeln('Iteration: ', i:1); repeat a := a + 1 until a = 10;
[edit] Procedures and functions
Pascal structures programs into procedures and functions.
program mine(output); var i : integer; procedure print(var j: integer); function next(k: integer): integer; begin next := k + 1 end; begin writeln('The total is: ', j); j := next(j) end; begin i := 1; while i <= 10 do print(i) end.
Procedures and functions can nest to any depth, and the 'program' construct is the logical outermost block.
Each procedure or function can have its own declarations of goto labels, constants, types, variables, and other procedures and functions, which must all be in that order. This ordering requirement was originally intended to allow efficient single-pass compilation. However, in most modern dialects the strict ordering requirement of declaration sections has been abandoned.
[edit] Resources
[edit] Compilers
Several Pascal compilers are available for the use of general public:
- Delphi is Borland's flagship RAD (Rapid Application Development) product. It uses the Object Pascal language (Dubbed the 'Delphi programming language' by Borland), descended from Pascal, to create applications for the windows platform. The latest versions 2005 and 2006 also support compiling to the .NET platform.
- Free Pascal (www.freepascal.org) is a multi-platform cross-compiler written in Pascal (so that it compiles itself). It is aimed at providing a convenient and powerful compiler, able both to compile legacy applications and to be the means of develop new ones. Also distributed freely under the GNU GPL. It can mix Standard Pascal, Extended Pascal (Turbo Pascal) and Object Pascal (Delphi) code together, and supports many platforms and operating systems.
- Dev-Pas (Dev-Pascal) is a Pascal compiler that was designed in Borland Delphi and is a Win32 compiler.
- Chrome (Chrome programming language) (website: www.chromesville.com) is a next generation Visual Studio plugin and stand-alone (in the .NET environment only) compiler for the Object Pascal language with the .NET and Mono Platforms. It was created and is sold by RemObjects Software.
- Kylix is Borland's newest reiteration of the Pascal branch of their products. It is the descendant of Delphi, with support for the Linux operating system and an improved object library. The compiler and the IDE are available now for non-commercial use. The product is currently no longer supported by Borland.
- GNU Pascal Compiler (GPC) is the Pascal compiler of the GNU Compiler Collection (GCC). The compiler itself is written in C, the runtime library mostly in Pascal. Distributed freely under the GNU General Public License, it runs on many platforms and operating systems. It supports the ANSI/ISO standard languages and partial Borland/Turbo Pascal language support. One of the more painful omissions is the absence of a 100% TP compatible string type. Support for Borland Delphi and other language variations is quite limited, except maybe for Mac Pascal, the support for which is growing fast.
- Virtual Pascal was created by Vitaly Miryanov in 1995 as a native OS/2 compiler compatible with Borland Pascal syntax. Then, it had been commercially developed by fPrint, adding Win32 support, and in 2000 it became freeware. Today it can compile for Win32, OS/2 and Linux, and is mostly compatible with Borland Pascal and Delphi. Development on this compiler was canceled on April 4, 2005.
- P4 compiler, the basis for many subsequent Pascal-implemented-in-Pascal compilers, including the UCSD p-System.
- Turbo Pascal was the dominant Pascal compiler for PCs during the 80s and early 90s, popular both because of its powerful extensions and extremely low compilation times. Turbo Pascal was compactly written and could compile, run, and debug all from memory without accessing disk. Slow floppy disk drives were common for programmers at the time, further magnifying Turbo Pascal's speed advantage. Currently, older versions of Turbo Pascal (up to 5.5) are available for free download from Borland's site.
- Dr. Pascal is an interpreter that runs Standard Pascal. Notable are the "visible execution" mode that shows a running program and its variables, and the extensive runtime error checking. Runs programs but does not produce a separate executable binary. Runs on MS-DOS, Windows in DOS window, and old Macintosh.
- IP Pascal Originally a Z80/CP/M Pascal that was ported and recoded for Intel 80386/PC, IP Pascal has a built-in portability library that is custom tailored to the Pascal language. For example, a standard text output application from 1970's original Pascal can be recompiled to work in a window and even have graphical constructs added. IP Pascal supports the ISO 7185 standard and upgrades the language logically. For example, original Pascal "padded right" strings are supported and integrated upwards seamlessly into dynamic strings. Standard Pascal static arrays are enhanced with dynamic arrays which are fully downward compatible with static arrays, etc.
- Pocket Studio is a Pascal subset compiler/RAD targeting Palm / MC68xxx with some own extensions to assist interfacing with the Palm OS API.
- MIDletPascal - A Pascal compiler and IDE that generates small and fast Java bytecode specifically designed to create software for mobiles
- Vector Pascal Vector Pascal is a language targeted at SIMD instruction sets such as the MMX and the AMD 3d Now, supporting all Intel and AMD processors, as well as the Sony Playstation 2 Emotion Engine.
- Morfik Pascal allows the development of Web applications entirely written in Object Pascal (both server and browser side).
A very extensive list can be found on Pascaland. The site is in French, but it is basically a list with URLs to compilers; there is little barrier for non-Francophones. The site, Pascal Central, a Mac centric Pascal info and advocacy site with a rich collection of article archives, plus links to many compilers and tutorials, may also be of interest.
[edit] Standards
In 1983, the language was standardized, in the international standard ISO/IEC 7185, as well as several local country specific standards, including the American ANSI/IEEE770X3.97-1983. In 1990, an extended Pascal standard was created as ISO/IEC 10206.
The ISO 7185 was stated to be a clarification of Wirth's 1974 language as detailed by the User Manual and Report [Jensen and Wirth], but was also notable for adding "Conformant Array Parameters" as a level 1 to the standard, level 0 being Pascal without Conformant Arrays.
Note that Niklaus Wirth himself referred to the 1974 language as "the Standard", for example, to differentiate it from the machine specific features of the CDC 6000 compiler.
On the large machines (mainframes and minicomputers) Pascal originated on, the standards were generally followed. On the IBM-PC, they were not. On IBM-PCs, the Borland standards Turbo Pascal and Delphi have the greatest number of users. Thus, it is typically important to understand whether a particular implementation corresponds to the original Pascal language, or a Borland dialect of it.
[edit] Divisions
Niklaus Wirth's Zurich version of Pascal was issued outside of ETH in two basic forms, the CDC 6000 compiler source, and a porting kit called Pascal-P system. The Pascal-P compiler left several features of the full language out. For example, procedures and functions as parameters, undiscriminated variant records, packing, dispose, interprocedural gotos and other features of the full compiler were left off.
UCSD Pascal, under professor Kenneth Bowles, used the Pascal-P2 kit, and consequentially had several of the same differences with the full Zurich Pascal compiler as the Pascal-P compiler did. UCSD Pascal later was adopted as Apple Pascal, and continued through several versions there.
Borland's Turbo Pascal, written by Anders Hejlsberg was written in assembly language independent of UCSD or the Zurich compilers. However, it adopted much of the same subset as the UCSD compiler, probably because at that time, UCSD was the most common Pascal system running on Microprocessors.
[edit] Criticism
While very popular (although more so in the 1980s and early 1990s than now), early versions of Pascal have been widely criticised for being unsuitable for "serious" use outside of teaching. Brian Kernighan, famed populariser of the C programming language, outlined his most notable criticisms of Pascal as early as 1981, in his paper Why Pascal Is Not My Favorite Programming Language. On the other hand, many major development efforts in the 1980s, such as for the Apple Lisa and Macintosh, heavily depended on Pascal (to the point where the C interface for the Macintosh operating system API had to deal in Pascal data types).
In the decades since then, Pascal has continued to evolve and most of Kernighan's points do not apply to current implementations. Unfortunately, just as Kernighan predicted in his article, most of the extensions to fix these issues were incompatible from compiler to compiler. In the last decade, however, the varieties seem to have condensed into two categories, ISO or Borland like, a better eventual outcome than Kernighan foresaw.
Based on his experience with Pascal (and earlier with ALGOL) Niklaus Wirth developed several more programming languages: Modula, Modula-2 and Oberon. These languages address some criticisms of Pascal, are intended for different user populations, and so on, but none has had the widespread impact on computer science and computer users as has Pascal, nor has any yet met with similar commercial success.
[edit] See also
- ALGOL
- C programming language
- Ada programming language: The United States Department of Defense's successor to Pascal, designed to be more feature-full and powerful
- Delphi programming language:
- Modula programming language: another, later, programming language design; intended for systems programming work
- Modula 2: a general purpose programming language, like Pascal (and unlike Modula), but Wirth has explicitly denied it was intended to be "Pascal's replacement"
- Oberon programming language: Wirth's object oriented successor to Modula 2
- Object Pascal
- Pascal and C: A comparison of Pascal and C.
- IP Pascal: A fully extended Pascal with built in graphical porting platform.
- Chrome programming language: An Object Pascal for the .Net framework.
[edit] External links
[edit] Reference material
- Bill Catambay, The Pascal Programming Language
[edit] Tutorials
[edit] Books
- Kathleen Jensen and Niklaus Wirth: PASCAL - User Manual and Report. Springer-Verlag, 1974, 1985, 1991, ISBN 0-387-97649-3 and ISBN 3-540-97649-3[1]
- also in N. Wirth, and A. I. Wasserman, ed: Programming Language Design. IEEE Computer Society Press, 1980
- You can find a free online Pascal book on Joe Dorward's website.
[edit] Journals
- Niklaus Wirth: The Programming Language Pascal. Acta Informatica, 1, (Jun 1971) 35-63
[edit] Resources
- Pascal Central — the one-stop Pascal resource site
- Standard Pascal — Resources and history of original, standard Pascal
- PASCAL XSC — The page of the developers of Pascal XSC with extensive material
- SWAG SourceWare Archive Group — collection of source code and program examples for the Pascal programming language
- Turbo-Pascal — free turbo pascal site
- Morfik Pascal — Pascal programming for Web applications (both server and browser side)
[edit] Standards
- Pascal standards ISO/IEC 10206: Extended Pascal
- ANSI-ISO Pascal ISO/IEC 7185: PASCAL
[edit] History
- N. Wirth, M. Broy, ed, and E. Denert, ed: Pascal and its Successors in Software Pioneers: Contributions to Software Engineering. Springer-Verlag, 2002, ISBN 3-540-43081-4
- N. Wirth: Recollections about the Development of Pascal. ACM SIGPLAN Notices, Volume 28, No 3, March 1993.
- Pascal User's Group Newsletters — An early Pascal history resource that contains many letters from Wirth and others concerning Pascal.
[edit] Criticism
[edit] Humor
- Real Programmers Don't Use Pascal — a joke about why real programmers don't use Pascal