Threads don't communicate.
They do their task and end, giving you the result.
As soon as you start "communications" threads would need to be able to run asyncronous within themself to handle the event like an interupt.
Thats not really the point of it, thats what scripts are for if you need it.
But a thread needs to run self contained. Use a thread manager if you need to change stuff on a thread. but that again would need threads to be objects so you could use setglobal, setlocal or whatever to alter stuff within the threads "memory space"
Your idea is more of a thing for which pub.freeprocess, TProcess.pipe and stdinStream / stdoutstream are used for.
They do their task and end, giving you the result.
As soon as you start "communications" threads would need to be able to run asyncronous within themself to handle the event like an interupt.
Thats not really the point of it, thats what scripts are for if you need it.
But a thread needs to run self contained. Use a thread manager if you need to change stuff on a thread. but that again would need threads to be objects so you could use setglobal, setlocal or whatever to alter stuff within the threads "memory space"
Your idea is more of a thing for which pub.freeprocess, TProcess.pipe and stdinStream / stdoutstream are used for.