|P is for Practical|
Err, you are using alias there in a completely different sense than it is usually used in perl
No data is stored in the alias, it is just a pointer (with some attached magic), to the actual SV containing the data. That's a little fatter than a RV used for aliasing, but not much.
In the sense tye was talking about, which has nothing to do with where a thread starts running, threads emulate fork
A few extracts from the wikipedia page:
You might just as well say that forking emulates spawning a thread. After all, fork does spawn a thread. They obviously have similarities, but that's the nature of the beast. But they also have differences.
So no. Spawning an iThread is not exactly the same as spawning a thread in C or assembler. But then spawning a thread in Java, (or Python or Ruby, or LUA or Clean or Pure or O'Caml or OZ or ... ) is not the same as in C either.
Likewise, Perl's arrays are slower and heavier than C's. In the same way as you don't have direct access to shared memory; you don't have direct access to integers floats or strings in Perl. You go through a layer of Perl internals code to get to both. And you reap the benefits from doing so, from both.
Perl's built-in fork emulates *nix fork on Win32 (and OS/2,); threads->new() does not emulate fork. It just does some things that are similar.
Tye's statement has little technical merit, but a lot of political intent.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.