Kbase P81679: How to change which include files are used when compiling on the fly
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
25/05/2004 |
|
Status: Unverified
GOAL:
How to change which include files are used when compiling on the fly
GOAL:
Why running the same external procedure with a different include file
GOAL:
How to flush rcode from memory
FIX:
When compiling on the fly, it is important to remember that by default the procedure only is compiled on the first run, and the compiled version is cached in memory.
This means that by default, switching include files used in that procedure will not take effect until the session ends.
To avoid this, force a recompile by adding a COMPILE statement before the RUN statement. For example:
OS-COPY include1.i includetouse.i. /* switch include file */
COMPILE called.p.
RUN called.p.