X-Git-Url: https://perl5.git.perl.org/perl5.git/blobdiff_plain/aadc0e04984c523115970b0a0c0ba40ddcee3d41..708e0e1d497b68c4abb0b9dfd8ea95ca3061c3e5:/pod/perlthrtut.pod diff --git a/pod/perlthrtut.pod b/pod/perlthrtut.pod index 00d5e57..cec07e0 100644 --- a/pod/perlthrtut.pod +++ b/pod/perlthrtut.pod @@ -1,3 +1,5 @@ +=encoding utf8 + =head1 NAME perlthrtut - Tutorial on threads in Perl @@ -5,13 +7,13 @@ perlthrtut - Tutorial on threads in Perl =head1 DESCRIPTION This tutorial describes the use of Perl interpreter threads (sometimes -referred to as I) that was first introduced in Perl 5.6.0. In this +referred to as I). In this model, each thread runs in its own Perl interpreter, and any data sharing between threads must be explicit. The user-level interface for I uses the L class. B: There was another older Perl threading flavor called the 5.005 model -that used the L class. This old model was known to have problems, is +that used the L class. This old model was known to have problems, is deprecated, and was removed for release 5.10. You are strongly encouraged to migrate any existing 5.005 threads code to the new model as soon as possible. @@ -109,7 +111,7 @@ looking for implementation details you're going to be either disappointed or confused. Possibly both. This is not to say that Perl threads are completely different from -everything that's ever come before -- they're not. Perl's threading +everything that's ever come before. They're not. Perl's threading model owes a lot to other thread models, especially POSIX. Just as Perl is not C, though, Perl threads are not POSIX threads. So if you find yourself looking for mutexes, or thread priorities, it's time to @@ -161,7 +163,7 @@ make threaded programming easier. =head2 Basic Thread Support -Thread support is a Perl compile-time option -- it's something that's +Thread support is a Perl compile-time option. It's something that's turned on or off when Perl is built at your site, rather than when your programs are compiled. If your Perl wasn't compiled with thread support enabled, then any attempt to use threads will fail. @@ -275,7 +277,7 @@ instead, as described next. NOTE: In the example above, the thread returns a list, thus necessitating that the thread creation call be made in list context (i.e., C). -See Ljoin()"> and L for more +See L<< threads/"$thr->join()" >> and L for more details on thread context and return values. =head2 Ignoring A Thread @@ -366,7 +368,7 @@ threading, or for that matter, to most other threading systems out there, is that by default, no data is shared. When a new Perl thread is created, all the data associated with the current thread is copied to the new thread, and is subsequently private to that new thread! -This is similar in feel to what happens when a UNIX process forks, +This is similar in feel to what happens when a Unix process forks, except that in this case, the data is just copied to a different part of memory within the same process rather than a real fork taking place. @@ -739,7 +741,7 @@ Semaphores with counters greater than one are also useful for establishing quotas. Say, for example, that you have a number of threads that can do I/O at once. You don't want all the threads reading or writing at once though, since that can potentially swamp -your I/O channels, or deplete your process' quota of filehandles. You +your I/O channels, or deplete your process's quota of filehandles. You can use a semaphore initialized to the number of concurrent I/O requests (or open files) that you want at any one time, and have your threads quietly block and unblock themselves. @@ -1003,7 +1005,7 @@ all the variables and data of the parent thread has to be taken. Thus, thread creation can be quite expensive, both in terms of memory usage and time spent in creation. The ideal way to reduce these costs is to have a relatively short number of long-lived threads, all created fairly early -on -- before the base thread has accumulated too much data. Of course, this +on (before the base thread has accumulated too much data). Of course, this may not always be possible, so compromises have to be made. However, after a thread has been created, its performance and extra memory usage should be little different than ordinary code. @@ -1030,7 +1032,7 @@ changing uids and gids. Thinking of mixing C and threads? Please lie down and wait until the feeling passes. Be aware that the semantics of C vary -between platforms. For example, some UNIX systems copy all the current +between platforms. For example, some Unix systems copy all the current threads into the child process, while others only copy the thread that called C. You have been warned! @@ -1041,7 +1043,7 @@ give you the full POSIX API). For example, there is no way to guarantee that a signal sent to a multi-threaded Perl application will get intercepted by any particular thread. (However, a recently added feature does provide the capability to send signals between -threads. See L for more details.) +threads. See L for more details.) =head1 Thread-Safety of System Libraries @@ -1049,9 +1051,8 @@ Whether various library calls are thread-safe is outside the control of Perl. Calls often suffering from not being thread-safe include: C, C, functions fetching user, group and network information (such as C, C, -C and so on), C, -C, and C -- in general, calls that depend on some global -external state. +C and so on), C, C, and C. In +general, calls that depend on some global external state. If the system Perl is compiled in has thread-safe variants of such calls, they will be used. Beyond that, Perl is at the mercy of @@ -1079,17 +1080,17 @@ on your way to becoming a threaded Perl expert. Annotated POD for L: L -Lastest version of L on CPAN: +Latest version of L on CPAN: L Annotated POD for L: L -Lastest version of L on CPAN: +Latest version of L on CPAN: L Perl threads mailing list: -L +L =head1 Bibliography @@ -1161,7 +1162,7 @@ Dan Sugalski Edan@sidhe.org Slightly modified by Arthur Bergman to fit the new thread model/module. -Reworked slightly by Jˆrg Walter Ejwalt@cpan.org to be more concise +Reworked slightly by Jörg Walter Ejwalt@cpan.org to be more concise about thread-safety of Perl code. Rearranged slightly by Elizabeth Mattijsen Eliz@dijkmat.nl to put