i think the problem here is that perls array type is so high level that you should really consider if you need an extra "List" container class or just return an array of "person" objects. in a "List" class you could add some extra functionality (whatever that may be), but you got to code it (extra code to maintain) - (i got the feeling that this sounds a bit like how you would do it in java?)
i have experienced that the places where you got to deal with one "object" and with a whole bunch of them is very clearly defined. there is IMO no reason to further generalize the code any more if you are at that stage.
if you have the time you may give the container class approach a try and make the decision for yourself which of the two suits you and the whole project best. just think on a popular perl saying :)
-
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.
|
