From: Jarkko Hietaniemi <jhi@iki.fi>
Date: Thu, 18 Jul 2002 19:13:53 +0000 (+0000)
Subject: Warn about mixing signals and threads;
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=b03ad8f690c4dcc613a1ec77d747e2d429945b16;p=p5sagit%2Fp5-mst-13.2.git

Warn about mixing signals and threads;
mention the comp.programming.threads FAQ.

p4raw-id: //depot/perl@17632
---

diff --git a/pod/perlthrtut.pod b/pod/perlthrtut.pod
index 25a4edf..cafcbb2 100644
--- a/pod/perlthrtut.pod
+++ b/pod/perlthrtut.pod
@@ -998,6 +998,11 @@ until the feeling passes-- but in case you really want to know,
 the semantics is that fork() duplicates all the threads.
 (In UNIX, at least, other platforms will do something different.)
 
+Similarly, mixing signals and threads should not be attempted.
+Implementations are platform-dependent, and even the POSIX
+semantics may not be what you expect (and Perl doesn't even
+give you the full POSIX API).
+
 =head1 Thread-Safety of System Libraries
 
 Whether various library calls are thread-safe is outside the control
@@ -1066,6 +1071,9 @@ Silberschatz, Abraham, and Peter B. Galvin. Operating System Concepts,
 Arnold, Ken and James Gosling. The Java Programming Language, 2nd
 ed. Addison-Wesley, 1998, ISBN 0-201-31006-6.
 
+comp.programming.threads FAQ,
+L<http://www.serpentine.com/~bos/threads-faq/>
+
 Le Sergent, T. and B. Berthomieu. "Incremental MultiThreaded Garbage
 Collection on Virtually Shared Memory Architectures" in Memory
 Management: Proc. of the International Workshop IWMM 92, St. Malo,