It is therefore not a "a separate process" in any way shape or form.
As has been explained to you *countless* times windows threads are used to emulate processes and those emulated processes are then used to emulate threads.
I don't know why I'm replying really because for some reason you're incapable of understanding this. Just because the perl interpreter is threaded doesn't mean userland perl has those same threads. This is a CLEAR distinction anyone with even the most basic of understanding can see. The threads you are referring to are windows threads created by C. That is not perl ithreads.
You're also disagreeing with Marc Lehmann who wrote Coro. What exactly have you written again? In fairness I think you just can't admit you're wrong. I certainly hope so for your sake as if you genuinely believe the things you're saying I fear for your intelligence and reading comprehension.
That's now 3 people who disagree with you including the author of Coro yet you still maintain your silliness. Everywhere I look I see you arguing with people. You really must enjoy it a lot. How sad.
Oh and please continue to show your maturity by negative rep'ing every reply I make here. What are you, 12 for goodness sake?
In reply to Re^10: Why Coro?
by binary
in thread Why Coro?
by xiaoyafeng
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |