Artur Bergman wrote:
> Even if so, I might be happy to use that subset of Perl in a threaded
> enviroment. Frankly I don't write code that deals alot with the system
> information, mostly my work is in IO and dealing with datastreams. I would
> be happy if this subset worked properly in threaded mode. I am going to try
> and get this to work for the subset of Perl I am using, I think that a group
> of people working in the same problem domain as I do will have uses of this
> threading.
You might be happy, I doubt your happiness will be universally shared. If
we say 'perl is threaded' prople will expect (and demand) correct behaviour
in all cases, not just in the restricted problem domain that you are
interested in.
> Perl does have an event loop, infact it has several of them. And I don't see
> how a event loop is going to help, one of the main reasons I am doing this
> is to run POE sessions in different threads.
Where? In perl-as-shipped?
As I don't know what POE is, I'm afraid your exact reasons for doing this
are no clearer.
> If this is such a big problem, then mod_perl is in for major breakage as
> mod_perl uses ithreads for mod_perl 2.0 and Apache 2.0, mod_perl is from my
> understand of major importance for perl, and if it will break badly then
> something needs to be done.
I wish them luck.
Alan Burlison
