summaryrefslogtreecommitdiff
path: root/pod/perltie.pod
diff options
context:
space:
mode:
authorPerl 5 Porters <perl5-porters@africa.nicoh.com>1996-03-11 07:12:46 +0000
committerCharles Bailey <bailey@genetics.upenn.edu>1996-03-11 07:12:46 +0000
commit03dc9dad76074724f481ba52b1330fbd20e39934 (patch)
tree6641aedbec91499037fb1164c30ab99ba9b83a9d /pod/perltie.pod
parent9b1b54d0581812b8017b125420e5d2fb98df5bed (diff)
downloadperl-03dc9dad76074724f481ba52b1330fbd20e39934.tar.gz
. . . and another typo gone.
Diffstat (limited to 'pod/perltie.pod')
-rw-r--r--pod/perltie.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perltie.pod b/pod/perltie.pod
index 90ac73926a..96f61eb436 100644
--- a/pod/perltie.pod
+++ b/pod/perltie.pod
@@ -218,7 +218,7 @@ anonymous ARRAY ref) will be accessed.
In our example, just to show you that you don't I<really> have to return an
ARRAY reference, we'll choose a HASH reference to represent our object.
A HASH works out well as a generic record type: the C<{BOUND}> field will
-store the maximum bound allowed, and the C<{ARRAY} field will hold the
+store the maximum bound allowed, and the C<{ARRAY}> field will hold the
true ARRAY ref. If someone outside the class tries to dereference the
object returned (doubtless thinking it an ARRAY ref), they'll blow up.
This just goes to show you that you should respect an object's privacy.