UCSD Pascal

related topics
{system, computer, user}
{math, number, function}
{work, book, publish}
{company, market, business}
{language, word, form}

UCSD Pascal was a Pascal programming language system that ran on the UCSD p-System portable, highly machine-independent operating system. The University of California, San Diego Institute for Information Systems developed it in 1978 to provide students with a common operating system that could run on any of the then available microcomputers as well as campus DEC PDP-11 minicomputers. UCSD p-System (Version IV, supplied by SofTech) was one of three operating systems (along with PC-DOS and CP/M-86) that IBM offered for its original IBM PC; but the p-System never sold very well for the IBM PC, mainly because of a lack of applications and because it was more expensive than the other choices. Previously, IBM had offered the UCSD p-System as an option for Displaywriter, an 8086-based dedicated word processing machine (not to be confused with IBM's DisplayWrite word processing software.) (The Displaywriter's native operating system had been developed completely internally and was not opened for end-user programming.)

Notable extensions to standard Pascal include separately compilable Units and a String type. Both of these extensions influenced the design of the Ada language.[1] Some intrinsics were provided to accelerate string processing (e.g. scanning in an array for a particular search pattern); other language extensions were provided to allow the UCSD p-System to be self-compiling and self-hosted.

UCSD Pascal was based on a p-code machine architecture. Its contribution to these early virtual machines was to extend p-code away from its roots as a compiler intermediate language into a full execution environment.[clarification needed] The UCSD Pascal p-Machine was optimized for the new small microcomputers with addressing restricted to 16-bit (only 64KB of memory). James Gosling cites UCSD Pascal as a key influence (along with the Smalltalk virtual machine) on the design of the Java virtual machine.

UCSD p-System achieved machine independence by defining a virtual machine, called the p-Machine (or pseudo-machine, which many users began to call the "Pascal-machine" like the OS—although UCSD documentation always used "pseudo-machine") with its own instruction set called p-code (or pseudo-code). Urs Ammann, a student of Niklaus Wirth, originally presented a p-code in his PhD thesis (see Urs Ammann, On Code Generation in a Pascal Compiler, Software—Practice and Experience, Vol. 7, No. 3, 1977, pp. 391–423), from which the UCSD implementation was derived, the Zurich Pascal-P implementation. The UCSD implementation changed the Zurich implementation to be "byte oriented". The UCSD p-code was optimized for execution of the Pascal programming language. Each hardware platform then only needed a p-code interpreter program written for it to port the entire p-System and all the tools to run on it. Later versions also included additional languages that compiled to the p-code base. For example, TeleSoft (also located in San Diego) offered an early Ada development environment that used p-code and was therefore able to run on a number of hardware platforms including the Motorola 68000, the System/370, and the Pascal MicroEngine.

Full article ▸

related documents
Complex instruction set computer
NewtonScript
Lotus 1-2-3
JFS (file system)
First-generation programming language
Lotus Symphony
Vim (text editor)
IA-32
PDP-11
FIFO
Web browser
Web service
PDP-1
Liberty BASIC
Direct-sequence spread spectrum
Blitz BASIC
Baudot code
Telephony Application Programming Interface
Break key
Intel 80286
Signal-to-noise ratio
Journaling file system
Motorola 6809
Graphics Device Interface
Intel 8086
Very-large-scale integration
GNU
MMX (instruction set)
Motorola 68020
Mbox