Iron Spring PL/I Compiler

Introduction

  pli-0.9.2
    |
    +-----------------------samples----------------lib
    |                          |                    |
 plic.exe                   (Sample sources and     +--------------------------static---include----source
 (compiler executable)       %include files,        PL/I DLL (prf.dll)         |         |         |
 (documentation, etc.)       sample makefiles       Import Library (prf.lib)   |         |         +--------asm
                             and module definition  (.obj files for all        |         |   (PL/I source)   |   
                             file).                  library procedures).      |         |               (assembler
                                                                               |  (%include files          source)
                                                                               |    required by                                                                                      
                                                                               |     library).
                                                                               |
                                                                      prf.lib (static library)
                                                                      OS2386.lib

Requirements

• OS/2 Warp 4 or higher. Warp 3 has been reported to work, but is unsupported.
• LINK386 linker or equivalent to link object files.
  LINK386 is distributed with OS/2 and installed as part of "Optional System Utilities."

Installation

1. Unpack the distribution file into a directory named "x:\pli-0.9.2", (Specify your desired drive in place of 'x'.)
2. Only the compiler (x:\pli-0.9.2\plic.exe) and either the static runtime library (x:\pli-0.9.2\lib\static\prf.lib) OR the DLL (x:\pli-0.9.2\lib\prf.dll) and the import library (x:\pli-0.9.2\lib\\prf.lib) are required. You should already have a version of OS2386.LIB. If you don't, you can use the one supplied in "x:\pli-0.9.2\lib\static\OS2386.lib".
3. Move the compiler to a directory in your PATH or add x:\pli-0.9.2 to your path in config.sys.
4. If you are using the DLL version of the library, move prf.dll to a directory in LIBPATH, or add (x:\pli-0.9.2\lib) to your LIBPATH in CONFIG.SYS and reboot. In order to link compiled programs you also need to make the import library prf.lib available by moving it to a directory listed in the LIB environment variable. Alternatatively, you can add the line "LIB = x:\pli-0.9.2\lib" to your makefiles.
5. If you are using the static version of the library (x:\pli-0.9.2\lib\static\prf.lib), move it [and x:\pli-0.9.2\lib\static\OS2386.lib if required] to a directory listed in the LIB environment variable. Alternatatively, you can add the line "LIB = x:\pli-0.9.2\lib\static" to your makefiles.
6. Test the sample programs. Two makefiles are provided: 'makefile' links with the DLL, 'makefile.static' links with the static library. CD to the directory "x:\pli-0.9.2\samples" and type "make" for the DLL version, or "make -f makefile.static" for the static version. If you don't have make available, you can manually type the commands in the makefile. The sample programs "numwrd", "filedump", "print_listing", and "libver" build to executables, the remainder should generate object files.
7. Test numwrd. Enter ".\numwrd 123". The program should display the result "one hundred twenty-three".
8. You might want access to the %INCLUDE files in "x:\pli-0.9.2\lib\include" or "x\pli-0.9.2\samples" for your own programming.

A later version will be installable using the WarpIN installer.

• Command should be contained on one line.
• Replace ${OBJ} with the name of your compiled object file (.obj)
• Replace ${LIBDIR} with the name of the directory containing the static library. For example, the default is \pli-0.9.2\lib\static
• Replace ${DEF} with the name of your module definition files (.def). See the LINK386 reference for a description of module definition files. This is not required for a VIO (non-PM) program, so it could be omitted and the ';' placed after 'OS2386.lib'.

The following command links a PL/I program with the PL/I runtime DLL.

LINK386 /m:f /a:8 /st:0x100000 ${OBJ},,,${LIBDIR}\prf.lib,${DEF};

• Command should be contained on one line.
• Replace ${OBJ} with the name of your compiled object file (.obj)
• Replace ${LIBDIR} with the name of the directory containing the PL/I runtime expore library. For example, the default is \pli-0.9.2\lib
• Replace ${DEF} with the name of your module definition files (.def). See the LINK386 reference for a description of module definition files. This is not required for a VIO (non-PM) program, so it could be omitted and the ';' placed after 'OS2386.lib'.
• The PL/I DLL must be in $LIBPATH when the program is executed.

A great deal of effort was made to ensure that the generated object code is identical to that produced by ALP in previous versions. No attempt has been made to improve the quality of the code, even in cases where improvements were identified. Although the instructions are identical the code is packaged somewhat differently in the object file. In most cases the files created by PL/I should be smaller than the corresponding file generated by ALP.

Because of this change the ALP asssembler has been changed from a required to an optional program. It is still required if you need to assemble the .asm output of the compiler or the assembler programs in the library.   Changes in version 0.6a The principal change is repackaging the library as both a DLL and a static library. The %REPLACE preprocessor statement has been implemented to provide limited support for named constants, pending implementation of the full preprocessor. The procedure and entry option FROMALIEN was added to allow 'callbacks' to PL/I procedures from C or assembler code.   Changes in version 0.5e Conversion between scaled FIXED BINARY and FIXED DECIMAL is now supported. PUT DATA has been largely implemented, except for arrays of structures. The COLUMN and SKIP format-items are now supported.   Changes in version 0.5d The compiler will now honor alternate characters for OR or NOT coded on the command line. Character strings can use either the single (') or the double (") quote characters as delimiters. All FIXED to FLOAT conversion routines now correctly handle constants and scaled values. The DEFINED attribute now accepts any valid reference as the base variable.

Modifying the Runtime Library