threads::shared::queue and semaphore become Thread::Semaphore

[p5sagit/p5-mst-13.2.git] / pod / perltooc.pod

diff --git a/pod/perltooc.pod b/pod/perltooc.pod
index c162220..fdddb02 100644 (file)
--- a/pod/perltooc.pod
+++ b/pod/perltooc.pod
@@ -646,7 +646,7 @@ name them whatever you care to.  Blindly and obediently using new()
 for each and every constructor you ever write is to speak Perl with
 such a severe C++ accent that you do a disservice to both languages.
 There's no reason to insist that each class have but one constructor,
-or that that constructor be named new(), or that that constructor be
+or that a constructor be named new(), or that a constructor be
 used solely as a class method and not an object method.
 
 The next section shows how useful it can be to further distance ourselves
@@ -1294,10 +1294,6 @@ Inheritance is a powerful but subtle device, best used only after careful
 forethought and design.  Aggregation instead of inheritance is often a
 better approach.
 
-We use the hypothetical our() syntax for package variables.  It works
-like C<use vars>, but looks like my().  It should be in this summer's
-major release (5.6) of perl--we hope.
-
 You can't use file-scoped lexicals in conjunction with the SelfLoader
 or the AutoLoader, because they alter the lexical scope in which the
 module's methods wind up getting compiled.