You probably want to examine perlreftut, but here are some thoughts. I'm not sure just how familiar you are with Perl, so you might want to check perldata just to see the datatypes (specifically, hashes and arrays). You may want to read those before proceeding with this post
That being said, you could represent this many ways.
- A 3D array, as you say, which would actually be an array of array references of array references. A possibility, but probably unnecessary, as your indices would be x,y,beans - and that would probably waste space (i.e. sparse)
- An array of hashrefs - this could contain something like an object. Each hashref could have the keys "x", "y" and "beans" and those values individually.
- Some combination of the two, e.g. an array of hasherefs of arrayrefs . Keys being "coordinates" (value of arrayref) and "beans" ( value being scalar)
I'm sure there are many more ways to represent this, but just don't want you to get "stuck" into thinking of just arrays. Perl is much more fun than that :)
--------------
"But what of all those sweet words you spoke in private?"
"Oh that's just what we call pillow talk, baby, that's all."
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|