diff options
author | Jarkko Hietaniemi <jhi@iki.fi> | 2002-05-12 19:48:40 +0000 |
---|---|---|
committer | Jarkko Hietaniemi <jhi@iki.fi> | 2002-05-12 19:48:40 +0000 |
commit | bdcfa4c71f2cdcdbe5f7cfb1837da43d4adcc767 (patch) | |
tree | 9aa7c3d0ce26a2335e4a4edd050e7cbdbf82c491 /pod/perlthrtut.pod | |
parent | 7830a95b315d7bb2736bca349d04df713036a763 (diff) | |
download | perl-bdcfa4c71f2cdcdbe5f7cfb1837da43d4adcc767.tar.gz |
Add threadsafety caveats.
p4raw-id: //depot/perl@16564
Diffstat (limited to 'pod/perlthrtut.pod')
-rw-r--r-- | pod/perlthrtut.pod | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/pod/perlthrtut.pod b/pod/perlthrtut.pod index 8bcbf24913..6a47e10937 100644 --- a/pod/perlthrtut.pod +++ b/pod/perlthrtut.pod @@ -955,6 +955,16 @@ be little different than ordinary code. Also note that under the current implementation, shared variables use a little more memory and are a little slower than ordinary variables. +=head1 Threadsafety of System Libraries + +Whether various library calls are threadsafe is outside the control +of Perl. Calls often suffering from not being threadsafe include +localtime(), gmtime(), get{gr,host,net,proto,serv,pw}*(), readdir(), +rand(), srand(). If the system Perl is compiled in has threadsafe +variants of these calls, they will be used, but besides that, Perl is +at the mercy of the thread safety or unsafety of the calls. Please +consult your C library call documentation. + =head1 Conclusion A complete thread tutorial could fill a book (and has, many times), |