One of the in-house modules I work with (and wrote) has
arrayrefs and hashrefs nested about six deep in places.
It's daunting when you look at it as a whole, but if you
deal with it as an aggregate of dependent parts, rather
than as a monolithic whole, it's quite manageable.
I tend to find that keeping track of several parallel
"simple" data structures is more complex and error-prone
than using a single, "complex" one. Inevitably, I modify
one of the related structures without modifying the others
in sympathy, and everything falls apart. (Maybe I'm
misunderstanding your point?)
--
The hell with paco, vote for Erudil!
:wq
-
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.
|