summaryrefslogtreecommitdiff
path: root/pod/perldsc.pod
diff options
context:
space:
mode:
authorRafael Garcia-Suarez <rgarciasuarez@gmail.com>2006-09-04 13:12:20 +0000
committerRafael Garcia-Suarez <rgarciasuarez@gmail.com>2006-09-04 13:12:20 +0000
commitb5d81ce9778c83ecbdeb300709817d34b87951c1 (patch)
tree46cebdc4c60587a19d05d4ca06a5000cc0a13534 /pod/perldsc.pod
parent630ad279b1b5cca7c05f94dc02339df068ae534a (diff)
downloadperl-b5d81ce9778c83ecbdeb300709817d34b87951c1.tar.gz
Documentation nit, found by Dr Ruud.
p4raw-id: //depot/perl@28780
Diffstat (limited to 'pod/perldsc.pod')
-rw-r--r--pod/perldsc.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perldsc.pod b/pod/perldsc.pod
index 158322b61c..fd6403b7e7 100644
--- a/pod/perldsc.pod
+++ b/pod/perldsc.pod
@@ -199,7 +199,7 @@ much harder to read:
Is it the same? Well, maybe so--and maybe not. The subtle difference
is that when you assign something in square brackets, you know for sure
it's always a brand new reference with a new I<copy> of the data.
-Something else could be going on in this new case with the C<@{$AoA[$i]}}>
+Something else could be going on in this new case with the C<@{$AoA[$i]}>
dereference on the left-hand-side of the assignment. It all depends on
whether C<$AoA[$i]> had been undefined to start with, or whether it
already contained a reference. If you had already populated @AoA with