"its own Perl interpreter" -- That tells us it's not really a thread, but a separate process

Each iThread, is simply another instance of the Perl interpreter running in it's own kernel thread within that same process.

It is therefore not a "a separate process" in any way shape or form.

"data sharing between threads must be explicit" -- And finally this tells us that they don't share address space

All threads, including iThreads share the same, single address space of the parent process. The iThreads model ensures that only data explicitly marked as shared can be accessed from multiple threads. This mechanism protects the programmer from accidental shared-state corruptions. This is the same as the way Perl protects the programmer from "pointer problems" by not giving him direct access to machine level pointers. With the same benefits.

so please refrain from attacks on me.

This is not an attack on you, but rather, (as always), a correction of misinformation you are disseminating.

As long as you feel the need to continue to do to disseminate such misinformation, I'll feel free to correct it.