Last changes: 2018-05-11
New compiler release 2018.05 available for VM/CMS, MVS (TK4-), Windows and OS/2.
The MVS (TK4-) installation procedure has been reworked (again)
Top feature of the new release:
- the Pascal/VS string datatype and its functions are now
available in the mainframe version of New Stanford Pascal, too;
all new string related P-Codes (beginning with the letter V, which stands for VarChar) have been successfully implemented,
that is: they are translated to inline 370 machine code most of the time.
Caution: because this implementation was a hard piece of work, there
may still be some errors in the string handling on the mainframe.
And: some runtime checks are not yet implemented, for example checks for the defined maximum length, so that overwriting of other storage areas
is still possible. This will be repaired in the mid term future.
If you don't use strings (or use them carefully), this version should be a very stable version.
The compiler compiling itself to 370 machine code on VM/CMS:
I am currently the maintainer of an improved version of the Stanford Pascal compiler.
The Stanford Pascal compiler is an offspring of the original Pascal P4 compiler, which was written in the 1970s at ETH Zurich by a team around Niklaus Wirth.
cited from english Wikipedia:
To propagate the language rapidly, 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 Pascal-P system.
The P-system compilers were termed Pascal-P1, Pascal-P2, Pascal-P3, and Pascal-P4.
Pascal-P1 was the first version, and Pascal-P4 was the last to come from Zurich.
A compiler based on the Pascal-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.
end of citation
The AAEC compiler later became the Stanford Pascal compiler (in 1979 ca.),
and later again,
it was maintained by the McGill university in Montreal, Canada (from 1982 on).
That's where I found it in 2011.
This page tells the story what happened from 2011 to today (not much
in the years 2011 to 2016),
what I did in the years since 2016, what I am doing now and what I will do in the future.
The compiler was originally targetted (since the AAEC days) to
IBM mainframes only.
Today it runs on VM/370 Rel.6 and on MVS 3.8j on the Hercules emulator.
And it runs on today's z/OS, too (tested first by Rene Jansen in 05.2017, thanks!).
It will sure run on modern zVM, too (at the moment limited to AMODE 24, RMODE 24).
The VM and MVS versions can be downloaded from this site (including source codes), see "Resources" below.
It also runs (tested) on Windows, OS/2, Linux (x86)
and Mac OS, because I ported it there in the end of 2016.
On these platforms the P-Code generated by the first compiler pass is interpreted by a P-Code interpreter written in ANSI-C,
so it will probably run on every platform that has a C compiler. Please contact me, if you want to test it on other platforms.
The Windows (and OS/2) version is available from this site, too; see "Resources" below.
You can follow the development process more closely on this Facebook page:
Stanford Pascal on Facebook
This picture shows the Pascal compiler compiling itself on Windows
(only pass 1 needed, Pascal to P-Code; the P-Code is interpreted by the P-Code interpreter PCINT).
Topics with this icon are not yet completed ... maybe implemented, but documentation is missing.
Warning: no warranty at all for the software contained here; I don't recommend that you use it for any production work. The AWS Tape file may contain an older version, which is not as current as the development stories from above. The source codes will be more current, but maybe you will not be able to compile them using the older versions on the AWS Tape, because it is sometimes necessary to apply incompatible extensions to the compiler. If I have time, I will put the new version to the AWS Tape, too (if the new version is stable enough).
If you have difficulties running or compiling the actual versions, contact me directly. I will help you as soon as I can, and I would like it if you test this compiler using some Pascal sources you maybe have.
The source code of the first pass: PASCAL1.PAS
The source code of the second pass: PASCAL2.PAS
The symbol scanner module: PASSCAN.PAS
Backup version 2018.02 first pass: PASCAL1A.PAS
Backup version 2018.02 second pass: PASCAL2A.PAS
To start Pascal programs using VM/CMS: XRUNPARM.ASS
The Pascal monitor and runtime: PASMONN.ASS
The source code of the LIBX library routines: PASLIBX.PAS
The source code of the UTILS library routines: PASUTILS.PAS
The source code of the MVS snapshot routine: PASSNAP.PAS
The source code of the CMS snapshot routine: PASSNAPC.PAS
The source code of the PASFORM source formatter utility: PASFORM.PAS
The source code of the XCOMP compare utility: XCOMP.PAS
Usage Notes for the MVS version:
the ZIP file contains an "Installation Guide" PDF, where you can find detailed instructions. You can also find it here.
The most recent version is available at GitHub:https://github.com/StanfordPascal/Pascal
Usage Notes for the Windows and OS/2 version:
Unzip the ZIP file from GitHub to a directory of your choice (or simply pull it).
The non-Mainframe versions of New Stanford Pascal are based on the P-Code interpreter PCINT.
I removed the precompiled executables PCINT.EXE (for Windows) and
PCINT2.EXE (for OS/2) from this site.
PCINT.EXE can easily be retrieved from the GitHub repository, too.
PCINT2.EXE for OS/2 is not contained in the GitHub repository any more.
The OS/2 variant of PCINT can be built from the Windows source in the GitHub repository,
using any C compiler. Look at aw.cmd to see, how to do it. If you need a OS/2 EXE
of the current PCINT, please contact me offline.
Recompiling PCINT is another option; use any C compiler you like.
I used IBM's C compiler on OS/2 and the Open Watcom C compiler on Windows (gcc on Linux, BTW).
Use PP <program> to call the Pascal compiler; the program should be stored in a file <program>.PAS
Use PRUN <program> to run the program
set DD_<logical_filename>=<physical_filename_including_path> to assign files
please contact me directly
(or: try to build a version of PCINT on the system you are interested in ...
take the sources from the GitHub repository above.
Please keep me informed, if you have successfully ported PCINT to another platform).
The Programming Language Pascal (Niklaus Wirth, 1972)
Stanford Pascal/360 Implementation Guide (1974)
P-Code Description (1978)
The Stanford Pascal compiler (1979)
The Implementation of Case Statements in Pascal (1981)
Pascal/VS Language Reference Manual (1981)
The Pascal ISO 7185 Standard (1991)
LE Stack and Heap Implementation (IBM 2005)
P-Code Description (2016)
External Procedures in Stanford Pascal - written in Pascal, FORTRAN or Assembler (2017)
P-Code Description (2017) - work in progress
Strings in New Stanford Pascal
New Stanford Pascal Installation Guide for MVS