Re^10: Why Coro?

Replies are listed 'Best First'.
Re^11: Why Coro? by ikegami (Patriarch) on Oct 27, 2010 at 23:50 UTC
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.* Perl threads (which has nothing to do with Windows) don't emulate threads. They may or may not be threads by your definition, but they definitely don't emulate threads. If they don't have the properties of (your definition of) threads, then they don't emulate threads. If they have the properties of (your definition of) threads, then they are threads, and thus can't emulate threads.	[reply]
A reply falls below the community's threshold of quality. You may see it by logging in.
Re^11: Why Coro? by Anonymous Monk on Oct 28, 2010 at 00:04 UTC
Ad-hominem attacks are not appropriate on this forum. Since Perl is open source, all you have to do is point at the source code portions that back up your claims.	[reply]
Re^12: Why Coro? by binary (Novice) on Oct 28, 2010 at 09:38 UTC
Exactly. Please scroll up and you'll see me point this out to browseruk who initially got personal for absolutely no reason.	[reply]
Re^13: Why Coro? by Anonymous Monk on Jan 03, 2011 at 08:24 UTC
I was talking to you binary. I have looked, and nowhere do you point at the source code portions that back up your claims. My understanding of win32 fork emulation and perl threads seems to agree with what BrowserUk is saying.	[reply]