summaryrefslogtreecommitdiff
path: root/lib/overload.pm
diff options
context:
space:
mode:
authorJeffrey Friedl <jfriedl@regex.info>2001-11-11 13:15:18 -0800
committerJarkko Hietaniemi <jhi@iki.fi>2001-11-12 14:50:44 +0000
commitd1be9408a3c14848d30728674452e191ba5fffaa (patch)
treed3171518bc3a517cf0c9ce65b5d8382c995f2fb6 /lib/overload.pm
parentbf0fa0b28861f64af680a3c19765ac8a24e4f2bd (diff)
downloadperl-d1be9408a3c14848d30728674452e191ba5fffaa.tar.gz
a few typo fixes
Message-Id: <200111120515.fAC5FIc74795@ventrue.corp.yahoo.com> Patching README.foo instead of pod/perlfoo.pod, not patching Math::BigInt (Tels will take care of that), dropping broken hv.c and sv.h patches, patching libnetcfg.PL and perldoc.PL instead of libnetcfg and perldoc, patching ext/Digest/MD5/t/files.t since MD5.pm was changed. p4raw-id: //depot/perl@12954
Diffstat (limited to 'lib/overload.pm')
-rw-r--r--lib/overload.pm8
1 files changed, 4 insertions, 4 deletions
diff --git a/lib/overload.pm b/lib/overload.pm
index 21a4b671ff..838c91fcee 100644
--- a/lib/overload.pm
+++ b/lib/overload.pm
@@ -298,7 +298,7 @@ if C<+=> is not overloaded.
=back
-B<Warning.> Due to the presense of assignment versions of operations,
+B<Warning.> Due to the presence of assignment versions of operations,
routines which may be called in assignment context may create
self-referential structures. Currently Perl will not free self-referential
structures until cycles are C<explicitly> broken. You may get problems
@@ -852,7 +852,7 @@ C<$a = $b> values of $a and $b become I<indistinguishable>.
On the other hand, anyone who has used algebraic notation knows the
expressive power of the arithmetic metaphor. Overloading works hard
to enable this metaphor while preserving the Perlian way as far as
-possible. Since it is not not possible to freely mix two contradicting
+possible. Since it is not possible to freely mix two contradicting
metaphors, overloading allows the arithmetic way to write things I<as
far as all the mutators are called via overloaded access only>. The
way it is done is described in L<Copy Constructor>.
@@ -969,7 +969,7 @@ TIEHASH() method is a scalar reference.
Second, we create a new tied hash each time the hash syntax is used.
This allows us not to worry about a possibility of a reference loop,
-would would lead to a memory leak.
+which would lead to a memory leak.
Both these problems can be cured. Say, if we want to overload hash
dereference on a reference to an object which is I<implemented> as a
@@ -1135,7 +1135,7 @@ which outputs
and one can inspect the value in debugger using all the possible
methods.
-Something is is still amiss: consider the loop variable $cnt of the
+Something is still amiss: consider the loop variable $cnt of the
script. It was a number, not an object. We cannot make this value of
type C<symbolic>, since then the loop will not terminate.