diff options
| author | Jarkko Hietaniemi <jhi@iki.fi> | 2002-07-13 00:03:04 +0000 |
|---|---|---|
| committer | Jarkko Hietaniemi <jhi@iki.fi> | 2002-07-13 00:03:04 +0000 |
| commit | 88f8c1dfe3e63f5bedaea1d870d5c68b59613b12 (patch) | |
| tree | f76987fee49b10ebf5c3c092efa2388ac0a1a473 /ext/threads | |
| parent | 3d32476b6ac7ae195aafe3bae3fdc0b9546c0e7a (diff) | |
| download | perl-88f8c1dfe3e63f5bedaea1d870d5c68b59613b12.tar.gz | |
Document that using threads/pseudofork inside BEGINs does not work.
p4raw-id: //depot/perl@17513
Diffstat (limited to 'ext/threads')
| -rwxr-xr-x | ext/threads/threads.pm | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/ext/threads/threads.pm b/ext/threads/threads.pm index 5fcbc9fd5c..337aaf5027 100755 --- a/ext/threads/threads.pm +++ b/ext/threads/threads.pm @@ -250,8 +250,19 @@ When you return an object the entire stash that the object is blessed as well. This will lead to a large memory usage. The ideal situation would be to detect the original stash if it existed. +=item Creating threads inside BEGIN blocks + +Creating threads inside BEGIN blocks (or during the compilation phase +in general) does not work. (In Windows, trying to use fork() inside +BEGIN blocks is an equally losing proposition, since it has been +implemented in very much the same way as threads.) + =item PERL_OLD_SIGNALS are not threadsafe, will not be. +If your Perl has been built with PERL_OLD_SIGNALS (one has +to explicitly add that symbol to ccflags, see C<perl -V>), +signal handling is not threadsafe. + =back =head1 AUTHOR and COPYRIGHT |