Related topics

FAIL DashProfiler-1.09 OpenBSD.i386-openbsd-thread-multi 4.1
Ther are some very strict rules about what can be shared between threads and what can't, and techniques for using critical sections. HTH Dave Francis "Martin" <nos...@spam.spam> wrote in message news:fi1dh9$5hv$1$8302bc10@news.demon.co.uk... Added DynLock() DynUnlock() and it runs fine until the DynUnlock when the

Threading & Events
As a result, replies you make to messages often spawn entirely new threads under a strict, reference-based threading system, even though threading by Subject: Because of this, unless I disable strict threading in slrn, your replies and subsequent followups to them show up in different threads elsewhere in the

FAIL EekBoek-1.03.09 i386-netbsd-thread-multi-64int 3.1
Please also email dbi-...@perl.org and include the output of 'perl -V' *** You are using a perl configured with threading enabled. ...... as a SCALAR ref while "strict refs" in use at /home/chris/blead/.cpanplus/5.11. 0/build/Data-ObjectDriver-0.05/blib/lib/Data/ObjectDriver/Driver/DBD.pm line 13.

Multi threading in perl
(i really hope so because this is bad news) if so, how can i work around that ? even though i keep it to a strict minimum, i REALLY REALLY need that @ in there ... how can i make this work safely? things that come to mind are: - locking that variable somehow, so the respective objects have to queue for using it.

Faux News...
The problem is the routine that creates this thread is never returned control after the join() has been called when the thread terminates. Sample Code : use strict; use warnings; missing. Please do read the posting guidelines for this group. They contain valuable information on how to help others help you. use

FAIL EekBoek-1.03.09 i386-netbsd-thread-multi-64int 3.1
There would probably be strict limits on what it could do, though. That is precisely the 1960s facility I am talking about. But why should it be restricted? In terms of implementation, it really needn't be very different from a function call with a little bit of extra hardware support for saving and restoring

FAIL Data-ObjectDriver-0.05 i686-linux-thread-multi-64int-ld 2.6 ...
Dear NAKAGAWA Masaki, This is a computer-generated report for XML-Atom-Ext-Threading-0.02 on perl 5.8.8, created by CPAN-Reporter-1.11. ..... 0-eou5mZ/blib/arch:/usr/local/src/CPAN/build/Class-Dot-1.5.0-eou5mZ/blib/lib:/usr/ local/src/CPAN/build/Test-Strict-0.09-5dhgIB/blib/arch:/usr/local/src/CPAN/build/Test-Strict

FAIL DBI-1.602 darwin-thread-multi-64int-2level 8.10.0
8333 NullP sth/s perl 5.010000 i386-netbsd-thread-multi-64int (gcc 3.3.3 -O) 0.000120s test.pl done [MSG] [Wed Feb 27 01:54:00 2008] Sending test report for 'DBI-1.602' ccflags ='-fno-strict-aliasing -pipe -I/usr/pkg/include', optimize='-O', cppflags='-fno-strict-aliasing -pipe -I/usr/pkg/include' ccversion='',

FAIL DBIx-NamedBinding-0.01 i686-linux-thread-multi-64int-ld 2.6 ...
Well, except in Microsoft... http://groups.google.com/group/comp.programming. threads/msg/52fbe7472d229061?hl=en http://groups.google.com/group/comp.programming. threads/browse_frm/thread/e7b5fe64cb35d64d/52fbe7472d229061?&hl=en#52fbe7472d229061 I hope that volatile does not become so strict that is rendered useless.

Gravity 2057 threading
Looks good I see you're using perl 5.010000 on i386-pc-solaris2.11-thread-multi-64int, okay. Remember to actually *read* the README file! ...... as a SCALAR ref while "strict refs" in use at /export/home/chris/perl5.10.0/.cpanplus/5.10. 0/build/Data-ObjectDriver-0.05/blib/lib/Data/ObjectDriver/Driver/DBD.pm line 13.

Possible Threading problem with -CURRENT / MySQL?
As of this post, the TB is 1.5, and believe me: it is fast, it looks beautiful, threading (strict, that is) works like a charm among thousands of other things (font control, HTML stripping/conversion to plain control, S/MIME, better SSL handling, USENET!, etc). I can assure you, you will not be dissappointed.

FAIL Fey-Test-0.02 darwin-thread-multi-64int-2level 8.10.0
4405 NullP sth/s perl 5.010000 darwin-thread-multi-64int-2level (gcc 4.0.1 -O3) 0.000227s test.pl done [MSG] [Mon Feb 25 23:17:26 2008] Sending test report .... uselongdouble=undef usemymalloc=n, bincompat5005=undef Compiler: cc='cc', ccflags ='-fno-common -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing -pipe

RFD: news.groups reorganization
usr/bin/perl #threads share same memory stack #each thread has it's own pid and stack pointer #threads can access other threads variables use threads; use threads::shared; use strict; my $wait = 500; my @up: shared; my $th; my @childs; my $child; my @down: shared; my @list = qw (5 10 15 20 25 30 35 40 45 50 55 60);

FAIL EekBoek-1.03.09 i686-linux-thread-multi-64int-ld 2.6.21.5-smp
You are using a perl configured with threading enabled. *** You should be aware that using multiple threads is *** not recommended for production environments. return value' [MSG] [Tue Feb 19 06:59:28 2008] cc -c -fno-strict-aliasing -I/usr/pkg/include -O -DVERSION=\"1.602\" -DXS_VERSION=\"1.602\" -DPIC -fPIC

FAIL ObjectDBI-0.11 i386-pc-solaris2.11-thread-multi-64int 2.11
I know from experience that the references line must be less than the two wrapped lines or it will fail. Certain versions of Tin are even worse, since they don't even notice that the headers are screwed. As to the subject threading, I prefer it to strict threading, since strict threading can obscure people's

Faux News...
4405 NullP sth/s perl 5.010000 darwin-thread-multi-64int-2level (gcc 4.0.1 -O3) 0.000227s test.pl done [MSG] [Tue Feb 26 23:23:32 2008] Sending test report ..... "strict refs" in use at /Volumes/Media/smoke/perl5.10.0/.cpanplus/5.10. 0/build/Data-ObjectDriver-0.05/blib/lib/Data/ObjectDriver/Driver/DBD.pm line 13.

FAIL DBIx-NamedBinding-0.01 darwin-thread-multi-64int-2level 8.10.0
You are using a perl configured with threading enabled. *** You should be aware that using multiple threads is *** not recommended for production environments. [MSG] [Wed Feb 27 08:11:02 2008] cc -c -pipe -fno-common -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing -I/usr/local/include -O3 -DVERSION=\"1.602\"

Strict threading on Mail.app
There would probably be strict limits on what it could do, though. If you want to make a system that will support Unix-style preemptive multitasking or I/O interrupts, you need EITHER precise exceptions to halt a running instruction stream in a well-defined place (but you don't mind precisely where) or you need a

FAIL Fey-Test-0.02 cygwin-thread-multi-64int 1.5.24(0.15642)
... t/zvxgp_80proxy.t t/zvxgp_85gofer.t t/zvxgp_86gofer_fail.t t/zvxgp_87gofer_cache.t I see you're using perl 5.008008 on darwin-thread-multi-64int-2level, [Sat Feb 16 12:26:38 2008] cc -c -fno-common -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing -pipe -Wdeclaration-after-statement -I/usr/local/include

FAIL Fey-Test-0.02 x86_64-linux-thread-multi-ld 2.6.22.10
... to rewrite call sites optimization and avoid some very tricky bugs with EMC and categories on multi-threading I felt that it is not the best way to spend my life. 2/ As we have previously discussed, I also like the idea of letting the developer decide on which parts he/she wants strict/dynamic typing.