I used the term 'forking' incorrectly, I apologize. What I should have said was it creates a new process. Which of course doesn't change the fact that ithreads are processes, not threads. They do not share memory. The documentation states this and code examples further support this. If you change 1 variable in 1 thread, it won't affect the variable with the same name in the same scope as another thread as it would with real threads. Try it for yourself.
Pasting a document about processes and threads from msdn has absolutely no bearing on the discussion at hand.
You're obviously extremely uncomfortable with yourself if you have to resort to personal attacks towards a faceless member on a forum. It is both immature and completely irrelevant to anything. It's known as "Ad Hominem" and it's a sign of intellectual weakness often used as a last resort to try and prove the conclusion.
But I'm not going to bother discussing this any further with you as when you stated that you don't think Coro is real threads it immediately showed me that you're lacking in the fundamentals and therefore are not in a position to discuss this let alone give advice.
Anyone else genuinely interested in knowledge and not proving a point can do more reading on some of the things I mentioned in my last post and they can test for themselves if variables are actually shared in ithreads. The documentation is quite clear though.
This is the last I'll comment on the matter as I do not wish to engage your ego further.
Good day to you.
In reply to Re^6: Why Coro?
by binary
in thread Why Coro?
by xiaoyafeng
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |