From 938aad412ad7b32d5a6a132b25ca095433d86c14 Mon Sep 17 00:00:00 2001 From: "Jerry D. Hedden" Date: Sun, 19 Aug 2007 09:53:17 -0400 Subject: [PATCH] Fix some typos in threads.pm From: "Jerry D. Hedden" Message-Id: <1ff86f510708191053x36f35619yaa019db70a623612@mail.gmail.com> p4raw-id: //depot/perl@31736 --- ext/threads/threads.pm | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/ext/threads/threads.pm b/ext/threads/threads.pm index e75d9d5..1fa0ee0 100755 --- a/ext/threads/threads.pm +++ b/ext/threads/threads.pm @@ -859,16 +859,16 @@ problem. =over -=item Threadsafe modules +=item Thread-safe modules See L when creating modules that may be used in threaded applications, especially if those modules use non-Perl data, or XS code. -=item Using non-threadsafe modules +=item Using non-thread-safe modules -Unfortunately, you may encounter Perl modules that are not I. For -example, they may crash the Perl interpreter during execution, or may dump +Unfortunately, you may encounter Perl modules that are not I. +For example, they may crash the Perl interpreter during execution, or may dump core on termination. Depending on the module and the requirements of your application, it may be possible to work around such difficulties. @@ -968,12 +968,12 @@ reconstituting it in the joining thread. =item Perl Bugs and the CPAN Version of L Support for threads extends beyond the code in this module (i.e., -F and F), and into the Perl iterpreter itself. Older +F and F), and into the Perl interpreter itself. Older versions of Perl contain bugs that may manifest themselves despite using the latest version of L from CPAN. There is no workaround for this other -than upgrading to the lastest version of Perl. +than upgrading to the latest version of Perl. -Even with the lastest version of Perl, it is known that certain constructs +Even with the latest version of Perl, it is known that certain constructs with threads may result in warning messages concerning leaked scalars or unreferenced scalars. However, such warnings are harmless, and may safely be ignored. -- 2.7.4