3 perllol - Manipulating Arrays of Arrays in Perl
7 =head2 Declaration and Access of Arrays of Arrays
9 The simplest thing to build is an array of arrays (sometimes imprecisely
10 called a list of lists). It's reasonably easy to understand, and
11 almost everything that applies here will also be applicable later
12 on with the fancier data structures.
14 An array of an array is just a regular old array @AoA that you can
15 get at with two subscripts, like C<$AoA[3][2]>. Here's a declaration
18 # assign to our array, an array of array references
21 [ "george", "jane", "elroy" ],
22 [ "homer", "marge", "bart" ],
28 Now you should be very careful that the outer bracket type
29 is a round one, that is, a parenthesis. That's because you're assigning to
30 an @array, so you need parentheses. If you wanted there I<not> to be an @AoA,
31 but rather just a reference to it, you could do something more like this:
33 # assign a reference to array of array references
35 [ "fred", "barney", "pebbles", "bambam", "dino", ],
36 [ "homer", "bart", "marge", "maggie", ],
37 [ "george", "jane", "elroy", "judy", ],
40 print $ref_to_AoA->[2][2];
42 Notice that the outer bracket type has changed, and so our access syntax
43 has also changed. That's because unlike C, in perl you can't freely
44 interchange arrays and references thereto. $ref_to_AoA is a reference to an
45 array, whereas @AoA is an array proper. Likewise, C<$AoA[2]> is not an
46 array, but an array ref. So how come you can write these:
51 instead of having to write these:
56 Well, that's because the rule is that on adjacent brackets only (whether
57 square or curly), you are free to omit the pointer dereferencing arrow.
58 But you cannot do so for the very first one if it's a scalar containing
59 a reference, which means that $ref_to_AoA always needs it.
61 =head2 Growing Your Own
63 That's all well and good for declaration of a fixed data structure,
64 but what if you wanted to add new elements on the fly, or build
65 it up entirely from scratch?
67 First, let's look at reading it in from a file. This is something like
68 adding a row at a time. We'll assume that there's a flat file in which
69 each line is a row and each word an element. If you're trying to develop an
70 @AoA array containing all these, here's the right way to do that:
77 You might also have loaded that from a function:
80 $AoA[$i] = [ somefunc($i) ];
83 Or you might have had a temporary variable sitting around with the
91 It's very important that you make sure to use the C<[]> array reference
92 constructor. That's because this will be very wrong:
96 You see, assigning a named array like that to a scalar just counts the
97 number of elements in @tmp, which probably isn't what you want.
99 If you are running under C<use strict>, you'll have to add some
100 declarations to make it happy:
109 Of course, you don't need the temporary array to have a name at all:
112 push @AoA, [ split ];
115 You also don't have to use push(). You could just make a direct assignment
116 if you knew where you wanted to put it:
118 my (@AoA, $i, $line);
121 $AoA[$i] = [ split ' ', $line ];
128 $AoA[$i] = [ split ' ', <> ];
131 You should in general be leery of using functions that could
132 potentially return lists in scalar context without explicitly stating
133 such. This would be clearer to the casual reader:
137 $AoA[$i] = [ split ' ', scalar(<>) ];
140 If you wanted to have a $ref_to_AoA variable as a reference to an array,
141 you'd have to do something like this:
144 push @$ref_to_AoA, [ split ];
147 Now you can add new rows. What about adding new columns? If you're
148 dealing with just matrices, it's often easiest to use simple assignment:
152 $AoA[$x][$y] = func($x, $y);
157 $AoA[$x][20] += func2($x);
160 It doesn't matter whether those elements are already
161 there or not: it'll gladly create them for you, setting
162 intervening elements to C<undef> as need be.
164 If you wanted just to append to a row, you'd have
165 to do something a bit funnier looking:
167 # add new columns to an existing row
168 push @{ $AoA[0] }, "wilma", "betty";
170 Notice that I I<couldn't> say just:
172 push $AoA[0], "wilma", "betty"; # WRONG!
174 In fact, that wouldn't even compile. How come? Because the argument
175 to push() must be a real array, not just a reference to such.
177 =head2 Access and Printing
179 Now it's time to print your data structure out. How
180 are you going to do that? Well, if you want only one
181 of the elements, it's trivial:
185 If you want to print the whole thing, though, you can't
190 because you'll get just references listed, and perl will never
191 automatically dereference things for you. Instead, you have to
192 roll yourself a loop or two. This prints the whole structure,
193 using the shell-style for() construct to loop across the outer
197 print "\t [ @$aref ],\n";
200 If you wanted to keep track of subscripts, you might do this:
202 for $i ( 0 .. $#AoA ) {
203 print "\t elt $i is [ @{$AoA[$i]} ],\n";
206 or maybe even this. Notice the inner loop.
208 for $i ( 0 .. $#AoA ) {
209 for $j ( 0 .. $#{$AoA[$i]} ) {
210 print "elt $i $j is $AoA[$i][$j]\n";
214 As you can see, it's getting a bit complicated. That's why
215 sometimes is easier to take a temporary on your way through:
217 for $i ( 0 .. $#AoA ) {
219 for $j ( 0 .. $#{$aref} ) {
220 print "elt $i $j is $AoA[$i][$j]\n";
224 Hmm... that's still a bit ugly. How about this:
226 for $i ( 0 .. $#AoA ) {
230 print "elt $i $j is $AoA[$i][$j]\n";
236 If you want to get at a slice (part of a row) in a multidimensional
237 array, you're going to have to do some fancy subscripting. That's
238 because while we have a nice synonym for single elements via the
239 pointer arrow for dereferencing, no such convenience exists for slices.
240 (Remember, of course, that you can always write a loop to do a slice
243 Here's how to do one operation using a loop. We'll assume an @AoA
248 for ($y = 7; $y < 13; $y++) {
249 push @part, $AoA[$x][$y];
252 That same loop could be replaced with a slice operation:
254 @part = @{ $AoA[4] } [ 7..12 ];
256 but as you might well imagine, this is pretty rough on the reader.
258 Ah, but what if you wanted a I<two-dimensional slice>, such as having
259 $x run from 4..8 and $y run from 7 to 12? Hmm... here's the simple way:
262 for ($startx = $x = 4; $x <= 8; $x++) {
263 for ($starty = $y = 7; $y <= 12; $y++) {
264 $newAoA[$x - $startx][$y - $starty] = $AoA[$x][$y];
268 We can reduce some of the looping through slices
270 for ($x = 4; $x <= 8; $x++) {
271 push @newAoA, [ @{ $AoA[$x] } [ 7..12 ] ];
274 If you were into Schwartzian Transforms, you would probably
275 have selected map for that
277 @newAoA = map { [ @{ $AoA[$_] } [ 7..12 ] ] } 4 .. 8;
279 Although if your manager accused of seeking job security (or rapid
280 insecurity) through inscrutable code, it would be hard to argue. :-)
281 If I were you, I'd put that in a function:
283 @newAoA = splice_2D( \@AoA, 4 => 8, 7 => 12 );
285 my $lrr = shift; # ref to array of array refs!
290 [ @{ $lrr->[$_] } [ $y_lo .. $y_hi ] ]
297 perldata(1), perlref(1), perldsc(1)
301 Tom Christiansen <F<tchrist@perl.com>>
303 Last update: Thu Jun 4 16:16:23 MDT 1998