In article <[log in to unmask]>, [log in to unmask]
(David Groves) writes:
 
>  I need to have a main process running which
>will use HPGETPROCPLABEL to enable new code items to execute, and I need
>to know whether the data objects being handled in the main process will
>be, or can be made to be, accessible by the new process
 
If the POSIX label is not important and this is a single process
dynamically calling external procedures/functions,  the tried and true
method is to have one source that is compiled with the $GLOBAL compiler
option and all others have the $EXTERNAL compiler option.
 
The only requirement here is that all source codes contain the same list
of global variables. If your compiler supports it, these globals can be
imported into all subprograms.  At a minimum, a single source can be
included in all subprograms. These external procedures can be LINKed into
an XL.
 
The program is run with the XL parameter where the dynamic procedures were
linked into.   There is some overhead in dynamically resolving the
external and parameter list that can be resolved at link time using this
method.
 
I must admit that our staff is puzzled by the description of Shared Global
Data also.  We are not sure if it refers to variable space reserved in the
XL, RL, or program data space.  If it only applies within a single
process, how is it different than traditional variables declared global in
scope??   I too would like clarification of this new feature in 5.0