My loadable module doesn't spawn threads but it does manage a great many
input files unknown to DX. State is saved until, of course, DX exits. The
trick is to design the module so it gets the job done within the DX
execution model. And, if you have more than one instance of the module, to
be able to send the right information to DX at each invocation. I'm using
4.3.2 under Fedora core 1.
Kent
--OnSeptember 21, 2004 04:30:31 PM <[EMAIL PROTECTED]> wrote:
My suggestion as always is
to build loadable modules since they tend to be faster (no latency when
starting and shutting down).
The module in question is used to couple a simulation with DX and thus
has to spawn a thread that survives the module's execution and with which
it shares static variables. I think I once unsuccessfully tried to
compile this as loadable. Does it make sense to try again or is this a
case that can only work with an outboard module?
