DN>> My take on this is that I would like to have a single executable
DN>> (e.g. E:\FORTRAN\BINP\PWB.EXE) and use it with different values
DN>> for PATH, INCLUDE and LIB. Thus, I could have a single copy of MS
DN>> Programmer's Work Bench with different behaviour running MS
DN>> FORTRAN, MS COBOL or IBM C/2 compilers.

MD> Why not put the name of your executable into a batch file (e.g.
MD> pwb_1.cmd, pwb_2.cmd etc.) with individual settings (SET
MD> BEGINLIBPATH=... and SET PATH=... followed by xyz.exe)?

No, the basic idea of this kind of WPProgram class is to avoid long PATH
and LIBPATH statements in CONFIG.SYS and, as far as I'm concerned, to avoid
different .CMD files for different command line sessions, too.

        // Albert  (Team OS/2)         email: jla{at}to.icl.fi

--- GoldED/2 2.50