This thread seems to be winding down fttb**, Judging from the below, perl multithreading [ I am guessing ] is simply syntatic sugar much the same as Koch C++ is a wrapper for regular cc compiler. This sounds nice, > Threading Perl bytecode would be nice about 98% of the time, and > should offer a speed increase. But from the operations industry perspective: > idioms like: > *main::localtime = \&localtime_replacement; ~and~ > if anything was overriden anywhere, no module code could be read in as bytecode, are issues esoteric enough to be avoided simply because of the cost of maintenance. Experience has also shown that an overdependance sophistication is a good way to wind up stranded waiting for a bugfix (I'm refering to financial ruin). If this is the case, the code underlying the treading would utilize normal functions to poll the concurrent event streams and programmers could choose between the threads and functions depending on their levels of comfort. This is good for my hypothetical remote sensing devices because the byte code interpreter would be single threaded, presumably smaller, and a lot easier to test. John ** like I'm going to tell you ;)
