jl>> I thought that your original intention was to set PATH and
jl>> LIBPATH for a specific program executable, not for a
jl>> program object.

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

DN> Likewise with some other OS/2 programs, and a few DOS programs.

DN> Thus, I would not want the environment information stored with the
DN> executable, but with each _instance_ of the program object.

Thanks! That seems to be the _only_ reasonable behaviour of such a program
object class.

Actually, the first prototype now stores it's PATH and ext-libpath just
like Jonathan suggested (using wpSaveState), but only because it was easier
to implement :-) I think I'll leave it that way .

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

--- GoldED/2 2.50