in reply to Re^2: Isolating dynamically loaded modules with Thread::Isolate.
in thread Isolating dynamically loaded modules with Thread::Isolate.

What we are doing here is a thread that can be used externally

I do not understand this statement?

, I can call things from outside inside this thread.

Nor this one? If I call into one thread, from another thread, does the calling thread block until the called thread completes? If so, the what is the thread doing for me? If not, how does this differ from starting the thread and then calling join to retrieve the results at some later point?

I've downloaded the module, read the pod and looked through the code, and I am a loss to understand as to what this module does beyond using eval to defer loading of modules until runtime? Which can be achieved using require and import.

I see lots of API, and Storable used to freeze something and then thaw it. I see lots of state that replicates state internal to

What I do not see is why I would use it?

This isn't critisism of the module--though it maybe of the documentation a little. It is just me trying to understand why I might use it. The examples do not make it clear to me what the module gets me?

Examine what is said, not who speaks.
Silence betokens consent.
Love the truth but pardon error.