Hello Jonathan!

10 Mar 96 23:20, Jonathan de Boyne Pollard wrote to Darin McBride:

 DM>>
 >> DM>
 >>   > JdeBP> C++ and EMXLOAD does for EMX C++.
 >>   >
 >>   > I would like to know how this is done - see if it can be
 >>   > done for Watcom as well.  :-)
 >> DM>
 >>
 >>  JdeBP> Use the EXEC_LOAD flag to DosExecPgm.  It's that
 >>  JdeBP> simple.
 >>
 >> Hey, neat.... :-)  Now, how would I UNLOAD it?
 DM>>

 JdBP>   DosKillProcess + DosWaitChild.

[alot of EMX problems deleted]

Woah... I guess you get what ya pay for, right?  ;-)

Anyway, my 'loader' for Watcom, if I can get to it, would be written with
Watcom anyway.  ;-)

 DM>>
 >> And how
 >> would I monitor its use so that I don't unload it while
 >> it's still being used?
 DM>>

 JdBP>   OS/2 will monitor its use.  No need for you to do so.  The code
 JdBP> will
 JdBP>   remain "loaded" until the last process using that code exits.

What I meant is ... EMXLOAD will only unload if the compiler has not been
used in the last x minutes.  I would like to know if WPP has been called in
the last x minutes - is there a way, short of checking the process list
every few seconds?

 DM>>
 >> Would the IDE still be able to call
 >> the pre-loaded version - without unloading it?
 DM>>

 JdBP>   The pre-loaded version isn't called at all.  What pre-loading
 JdBP> does is to
 JdBP>   eliminate all of the time that the OS/2 process loader would
 JdBP> otherwise
 JdBP>   spend creating module images and searching along LIBPATH for
 JdBP> DLLs. It
 JdBP>   also helps carry over the working set information for the
 JdBP> process to
 JdBP>   successive invocations of the program.

Thanks alot... this helps my understanding greatly.  :-)

Darin McBride

--- GoldED/2 2.42.G0614