diff options
| author | Tom Christiansen <tchrist@perl.com> | 2010-01-04 20:32:51 -0700 |
|---|---|---|
| committer | Abigail <abigail@abigail.be> | 2010-01-05 09:24:38 +0100 |
| commit | e10204135b763e864169cd1f19037fc2f8c37385 (patch) | |
| tree | f464a387ef72dad8ba3a19d05a412d9b4464cbaf /pod/perlthrtut.pod | |
| parent | 1a64a5e6c710ac493fe0339fdf240f512a934369 (diff) | |
| download | perl-e10204135b763e864169cd1f19037fc2f8c37385.tar.gz | |
PATCH: minor typo cleanup of pod/ directory
These are all in the pod/ directory, and only the first is a code fix.
There was also a single lingering ISO 8859-1 encoding that missed the
UTF-8 upconvert. The rest are cleanups for typos, some of which seem
to have been around for a rather long time: spelling errors, incorrect
possessives, and extra, missing, or duplicated words.
If you actually read through, I bet you'll realize what sparked this. :)
--tom
Signed-off-by: Abigail <abigail@abigail.be>
Diffstat (limited to 'pod/perlthrtut.pod')
| -rw-r--r-- | pod/perlthrtut.pod | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/pod/perlthrtut.pod b/pod/perlthrtut.pod index 00d5e57dcc..63dcb841e4 100644 --- a/pod/perlthrtut.pod +++ b/pod/perlthrtut.pod @@ -366,7 +366,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 +739,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. @@ -1030,7 +1030,7 @@ changing uids and gids. Thinking of mixing C<fork()> and threads? Please lie down and wait until the feeling passes. Be aware that the semantics of C<fork()> 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<fork()>. You have been warned! @@ -1161,7 +1161,7 @@ Dan Sugalski E<lt>dan@sidhe.org<gt> Slightly modified by Arthur Bergman to fit the new thread model/module. -Reworked slightly by Jˆrg Walter E<lt>jwalt@cpan.org<gt> to be more concise +Reworked slightly by Jörg Walter E<lt>jwalt@cpan.org<gt> to be more concise about thread-safety of Perl code. Rearranged slightly by Elizabeth Mattijsen E<lt>liz@dijkmat.nl<gt> to put |