diff options
author | Richard Soderberg <p5-authors@crystalflame.net> | 2004-11-12 16:14:49 +0000 |
---|---|---|
committer | H.Merijn Brand <h.m.brand@xs4all.nl> | 2004-11-12 20:47:19 +0000 |
commit | fa11829f4b6d56533794dd127f3d1068d9593670 (patch) | |
tree | 7f368b0c4f3bed68b378d9fea31eee156223ea2c /pod/perlthrtut.pod | |
parent | ac7de224d1cdf1bc265fb1a3311a78c903d66ee7 (diff) | |
download | perl-fa11829f4b6d56533794dd127f3d1068d9593670.tar.gz |
[perl #32419] Spelling fixes for perl@23492
From: Richard Soderberg (via RT) <perlbug-followup@perl.org>
Message-ID: <rt-3.0.11-32419-100173.13.0717895191322@perl.org>
p4raw-id: //depot/perl@23496
Diffstat (limited to 'pod/perlthrtut.pod')
-rw-r--r-- | pod/perlthrtut.pod | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlthrtut.pod b/pod/perlthrtut.pod index 517fdd1b86..8e4e4f6063 100644 --- a/pod/perlthrtut.pod +++ b/pod/perlthrtut.pod @@ -602,7 +602,7 @@ communications between threads. =head2 Semaphores: Synchronizing Data Access Semaphores are a kind of generic locking mechanism. In their most basic -form, they behave very much like lockable scalars, except that thay +form, they behave very much like lockable scalars, except that they can't hold data, and that they must be explicitly unlocked. In their advanced form, they act like a kind of counter, and can allow multiple threads to have the 'lock' at any one time. |